mail.matt.mcdonald at gmail.com
Thu Feb 1 19:20:51 EST 2007
I just got it to build with cygwin, xsp works, looks like it's time to dig
in. Right now I'm planning on using a Windows box to write the .NET 2.0 unit
tests and a OpenSuse Linux box to actually test the Mono implementation
(when the time comes).
One final question before I dig in: On a Linux machine, Is is appropriate to
use apache+mod_mono to test web assemblies, or should XSP always be used?
Thanks a lot for bearing with me as I come up to speed on how things work
On 2/1/07, Miguel de Icaza <miguel at novell.com> wrote:
> > Sounds like a plan.
> > I'm a complete neophyte when it comes to contributing to mono (though
> > I've been using and following the project for some time), what's the
> > best way to submit test cases to the project?
> There are a few things you will want to do:
> 1. Make sure you can build Mono from SVN yourself, this is
> so that you have all the tools in place, and you can test
> 2. Make sure you can run `xsp' on sample pages.
> Once you do that, I suggest that you get yourself NUnit, and write a
> small test case for the first class you pick (pick something easy
> first). You can see a bunch of samples in mcs/class/System.Web/Test/
> directory. We use a file per class to test.
> This will help you understand the API beyond the documentation
> description: you will understand the inputs, the outputs, what things
> must be checked and what must not.
> Then you run this with NUnit and you make sure it works on Windows. At
> that point you can write your implementation for Mono. Never looking
> at decompiled output, never using a disassembler or any other tools but
> public documentation and public Microsoft blogs (avoid reverse
> engineering sites).
> Then you can contribute your tests and your classes (send us an email).
> Once you are comfortable with it, we give you an SVN account.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list