Miguel de Icaza
miguel at novell.com
Fri Feb 2 13:54:51 EST 2007
> You can put the files under olive/class for each assembly you hack,
> and on your assembly's top directory, you can run "make" to build the
> assembly (it will be generated under olive/class/lib/net_3_0, though
> it's not really 3.0 stuff), "make test" to build unit tests (dll),
> and "make run-test" to actually run the tests. And optionally "make
> run-test-ondotnet" to run your test under Microsoft.NET so that your
> tests actually assures expected results (unless .NET behavior is not
> bogus). atlas.pub is to be put under olive/class.
> (I'm not likely to work on it, so in case you use them feel free to
> replace those files when you are done with your own implementation :-)
Would you mind checking this code into Olive, just to get a base line
that others can reuse?
> Hope this helps.
> Atsushi Eno
> Matthew McDonald wrote:
> > Hi,
> > 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 around here.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list