NUnit assemblies for .NET 2.0

"Charlie Poole" <[email protected]> Fri, 28 Mar 2008 13:05:44 -0700
Newsgroups gmane.comp.windows.dotnet.nunit.devel
Message-ID <012001c8910f$1bbedf90$6401a8c0@ferrari>
Hi All,

Up to now, all NUnit assemblies were built using multiple versions
of .NET and Mono, but contained identical source code. They were 
all given the same names and versions and that worked.

Moving ahead, that changes. I see two sorts of change...

1) Assemblies that continue to do the same thing as viewed
by their callers, but have differing interal implementations
for .NET 2.0 and above. I see doing some of this in the 
test-loading code to improve efficiency under .NET 2.0.

2) Assemblies that expose new features in their .NET 2.0
versions. For example, having Assert.Throws<T> in the
2.0 framework assembly.

My tentative view is that assemblies in the first category
can continue to have the same name and version, only being
distinguished by the runtime for which they were built.

I'm less certain in the second case. For the framework,
as an example, we could have nunit.framework.dll and 
nunit.framework2.dll. Alteratively, we could distribute
different versions with each package, calling both of 
them nunit.framework. What will work best?

Charlie




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace