Ah ha! I saw nunit-console.dll in your post and assumed you had re-written the console program for some reason. Now I'm less confused. :-)
Charlie > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Atsushi Eno > Sent: Tuesday, November 25, 2008 12:06 AM > To: [email protected]; [EMAIL PROTECTED] > Subject: SPAM-LOW: Re: [Mono-list] NUnit Version - Upgrade soon? > > Actually it turned out to be my bogus Makefile that assumed > nunit-console-runner.dll is nunit-console.dll, which was > conflicting nunit-console.exe and hence type loading failure > happened (and turned out that it should fail since foo.dll > and foo.exe cannot coexist). > > Now I have a fixed version of nunit for our own use: > http://veritas-vos-liberabit.com/tmp/2008/nunit24-mono.tar.bz2 > > If no problem, I'll checkin this new nunit24 directory and > build changes, without removing nunit20 for a while. > > Atsushi Eno > > > It is anything but negative approach. As I wrote earlier, I believe > > this is a mono bug that likely hits other projects and > should be fixed > > in mono land. > > > > I'll try to cook a repro and file a bug. > > > > For the record, there is almost no change in NUnit code in > my archive. > > We just have to change AssemblyInfo (assembly key location), remove > > tests (they are extra in our source tree) and extra stuff > such as GUI. > > It is straightforward upstream code. Believe or not, just > diff them ;) > > > > Atsushi Eno > > > > > > Charlie Poole wrote: > >> I think a more positive approach would be to work with the NUnit > >> project so that you can just use the upstream code. > >> > >> Charlie > >> > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED] On Behalf Of > Atsushi Eno > >>> Sent: Saturday, November 22, 2008 4:30 PM > >>> To: [email protected] > >>> Subject: SPAM-LOW: Re: [Mono-list] NUnit Version - Upgrade soon? > >>> > >>> You almost do not have to do that: > >>> http://veritas-vos-liberabit.com/tmp/2008/nunit24-mono.tar.bz2 > >>> > >>> It builds but does not work anyways right now, probably > because of > >>> some type resolution bugs between nunit-console.dll and > >>> nunit-console.exe. > >>> > >>> If you have patch for mono (diff in mono/mcs, not diff in > >>> nunit) to fix any issues, that is welcome. > >>> > >>> Atsushi Eno > >>> > >>> > >>> Michael Franz wrote: > >>>> OK, > >>>> > >>>> I thought I read somewhere that there were patches to NUnit > >>> that were > >>>> mono specific. > >>>> > >>>> Is it ok to submit patches to mono that depend on the > >>> latest version > >>>> of NUnit? > >>>> > >>>> Michael > >>>> > >>>> On Tue, Nov 18, 2008 at 3:25 PM, Miguel de Icaza > <[EMAIL PROTECTED] > >>>> <mailto:[EMAIL PROTECTED]>> wrote: > >>>> > >>>> Hello, > >>>> > >>>> > What changes to NUnit were specific to Mono? > >>>> > > >>>> > Is there a list of these features? > >>>> > >>>> You are confused; There are no changes, you should > >>> just not depend on > >>>> Mono's built-in and private copy of NUnit to write your > >>> NUnit test > >>>> cases. > >>>> > >>>> You should get the latest NUnit. > >>>> > >>>> > On Sun, Nov 16, 2008 at 10:54 PM, Miguel de Icaza > >>>> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > >>>> > wrote: > >>>> > Hello, > >>>> > > >>>> > > >>>> > > I use NUnit for work and have been using > >>> the latest version > >>>> > for > >>>> > > months. I wrote some test for Mono and > >>> found out that the > >>>> > version > >>>> > > that Mono is using does not support some > >>> of the asserts > >>>> I am > >>>> > using > >>>> > > (IsEmpty). Is there any plan to upgrade > >>> the version of > >>>> > NUnit that is > >>>> > > used with the Mono build/test? > >>>> > > >>>> > > >>>> > The NUnit that ships with Mono should be > considered > >>>> Mono's own > >>>> > copy of > >>>> > NUnit and not a public version of it. > >>>> > > >>>> > We should probably make packages of the > >>> latest version of > >>>> > NUnit, > >>>> > encourage the NUnit developer to maintain > >>> those and encourage > >>>> > developers > >>>> > to use the public NUnit as opposed to the > >>> private copy that > >>>> > Mono ships. > >>>> > > >>>> > > >>>> > >>>> > >>>> > >>>> > >>> > -------------------------------------------------------------------- > >>> -- > >>>> -- > >>>> > >>>> _______________________________________________ > >>>> Mono-list maillist - [email protected] > >>>> http://lists.ximian.com/mailman/listinfo/mono-list > >>> _______________________________________________ > >>> Mono-list maillist - [email protected] > >>> http://lists.ximian.com/mailman/listinfo/mono-list > >>> > >> > >> > >> _______________________________________________ > >> Mono-list maillist - [email protected] > >> http://lists.ximian.com/mailman/listinfo/mono-list > >> > > > > _______________________________________________ > > Mono-list maillist - [email protected] > > http://lists.ximian.com/mailman/listinfo/mono-list > > > > _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
