[Mono-devel-list] NUnit 2.1 for Mono - status and questions

Charlie Poole cpoole at pooleconsulting.com
Sat Oct 18 12:37:43 EDT 2003

Thanks, I'll go with it then... 

If there are any glitches, you can fix them. :-)

Charlie Poole
cpoole at pooleconsulting.com

-----Original Message-----
From: Jonathan Pryor [mailto:jonpryor at vt.edu] 
Sent: Friday, October 17, 2003 4:32 PM
To: Charlie Poole
Cc: Mono Development List
Subject: Re: [Mono-devel-list] NUnit 2.1 for Mono - status and questions

To answer your final question (does Mono support IsolatedStorage), Mono
does have an implementation.

I won't make any claims to it being the best and most tested
implementation known to man, but it should be enough to get you going. 
I hope.  (I coded it up in a day; it allows at least one example from
"Programming C#" to compile & run.  Famous last words?)

 - Jon

On Fri, 2003-10-17 at 15:48, Charlie Poole wrote:
> Hi all,
> This note contains (1) status of the mono release of NUnit 2.1, (2) a
> list of differences between that release and the windows release so
> and (3) some specific questions I have.
> 1. Status
> I have a build that appears to work at least insofar as I can test it.
> I'll make a link available this weekend for those willing to try it
> and give me some feedback.
> This build will be initially separate from the downloads on
> and I will maintain it as a private branch. Once I know it's stable, I
> expect to merge it in with the nunit sourceforge code using
> compilation where necessary.
> I expect the mono distribution to be a separate package on sourceforge
> by some point in November. I see it as source code only at this point.
> 2. Differences
> The following assemblies are not included in the Mono release:
> 	nunit-gui	(the Windows forms gui)
> 	nunit.uikit	(Windows forms support dll)
> 	cpp-sample	(sample app)
> 	jsharp	(sample app)
> 	vb-sample	(sample app)
> 	install	(Windows msi builder)
> The nunit.framework assembly is split into nunit.core and
> unit.framework. This is in nunit's cvs tree and will be in the next
> windows release as well. The framework assembly is for reference by
> tests, the core assembly is for use by client code like gui runners,
> etc.
> The nunit.util assembly no longer contains references to the Windows
> registry. It /does/ contain code to open Visual Studio .NET projects
> solutions. That code should work even on a linux OS since it merely
> reads the files and doesn't depend on Visual Studio at all.
> 3. Questions
> I have a Windows install of mono but not from source. Can I use this
> perform some verification myself? Is there a doc that will get me
> started quickly? I do plan to set up a separate machine in the near
> future but I don't have a major amount of time right now, so if I have
> to build mono from source to do this I'll just rely on you folks to
> problems.
> The initial release for mono won't have (or need) any optional
> but they will be needed at some point. I'd like to migrate the
> for nunit to a more portable implementation. Does mono support
> IsolatedStorage? If not, what approach would you favor?
> Any other questions or comments on the above?
> Charlie Poole
> cpoole at pooleconsulting.com
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list