Fri Feb 8 08:55:55 EST 2008
nunit files are not actually included in the mono build even though they
are in cvs. As it turns out, we no longer have any non-gui registry
settings, so I'll just proceed as planned and drop those things. We
want to get away from the registry anyway, so we should be able to
merge the two builds in the next release of nunit.
cpoole at pooleconsulting.com
> -----Original Message-----
> From: Nick Drochak [mailto:ndrochak at gol.com]
> Sent: Tuesday, October 14, 2003 10:10 AM
> To: 'Charlie Poole'; mono-devel-list at lists.ximian.com
> Subject: RE: [Mono-devel-list] NUnit 2.1
> | -----Original Message-----
> | From: Charlie Poole [mailto:cpoole at pooleconsulting.com]
> | Sent: Wednesday, October 15, 2003 1:13 AM
> | To: ndrochak at gol.com; mono-devel-list at lists.ximian.com
> | Subject: RE: [Mono-devel-list] NUnit 2.1
> | > I assume the registry support is for the GUI, like a "Recent
> Tests" menu
> | > item. We don't have the GUI in mono CVS, so if you need a quick build
> | > it might be enough to just delete those files. I haven't tried it
> | > however.
> | Most of it is gui related, and I can work around the rest. That's what I
> | doing till I noticed your CVS actually contains the code that
> accesses the
> | windows registry and saw a note that seemed to indicate it
> builds. That's
> | the
> | part that's confusing me. I don't want to release an nunit for mono that
> | less capability than what you guys are already doing.
> Well, we never used the windows GUI of NUnit with mono testing.
> At least we
> never really had it in CVS. We have just used nunit-console
> until now; and
> also gnunit.
> It definitely was building on linux before, but I don't think
> those classes
> were used at all by the mono runtime since we didn't use the GUI runner.
> In other words, I don't think we lose anything if you take out
> the registry
> Nick D.
More information about the Mono-devel-list