SPAM-LOW: [Mono-dev] FW: [nunit-developer] NUnit Version Numbering

Charlie Poole charlie at
Sat Dec 3 13:29:58 EST 2005

Hi All, 

I haven't had any comments from this list on the latest versioning status,
but someone on the developer list has stated that failing to distinguish
builds by version number is a problem for mono. If it is, I'd like to know
for sure.

On Windows, NUnit is not installed in the GAC with the exception of the
nunit.framework assembly. We're discussing removing that from the GAC in
order to simplify deployment. When a particular version of nunit-gui or
nunit-console is run, it uses private copies of all the assemblies. I'm able
to run the 1.1 and 2.0 builds of NUnit 2.2.3 side by side with no problem on
my Windows system. The 2.0 version can even run the NUnit tests from the 1.1
version. The framework in the GAC is, of course, the last one installed, but
this doesn't cause a problem either, since the code doesn't yet use any 2.0

My understanding is that it's different on Mono, because it runs NUnit out
of the GAC. What I don't understand is if or why this is necessary. If this
is too much to explain to me on the list, I'd appreciate someone
volunteering to work with me offline.

Of course, if there comes a time when NUnit sports different features under
2.0, that will change things. Right now, I'm only talking about
distinguishing between builds that are identical except for the CLR version
they were built with.


> -----Original Message-----
> From: mono-devel-list-bounces at [mailto:mono-devel-list-
> bounces at] On Behalf Of Charlie Poole
> Sent: Tuesday, November 29, 2005 5:12 AM
> To: mono-devel-list at
> Subject: SPAM-LOW: [Mono-dev] FW: [nunit-developer] NUnit Version
> Numbering
> Hi All,
> I just posted this to the nunit developer list. We had a brief discussion
> on
> this list about using version numbers to distinguish the 1.1 and 2.0
> builds
> of NUnit. As you'll see below, I'm not doing that at the moment, but I'm
> open to suggestions.
> Charlie
> -----Original Message-----
> From: nunit-developer-admin at
> [mailto:nunit-developer-admin at] On Behalf Of Charlie
> Poole
> Sent: Monday, November 28, 2005 3:41 PM
> To: nunit-developer at
> Subject: RE: [nunit-developer] NUnit Version Numbering
> Hi All,
> Following up on the version numbering issue, here's what's happening...
> 1. NUnit 2.2.3 was released in two builds, one using .Net 1.1 and the
> other
> using .Net 2.0. The same version number was used for both versions and
> this
> seems to cause no problems. Please let me know if any are encountered.
> 2. NUnit will go to the traditional odd/even numbering used in many open
> source projects. For example: 2.3.x is a development build and 2.4.x is a
> stable production build.
> 3. The build number (third digit) for development builds will be in the
> form
> yddd, representing the date of the build. For example, a development build
> issued today would be 2.3.5322, one a week from now would be 2.3.5329.
> 4. The build number for stable builds will be sequential within each minor
> version: 2.4.1, 2.4.2, etc.
> 5. The CVS mainline will always contain the version number of the last
> development drop. We'll use a release branch for stable releases and will
> begin doing bug fixes on those releases, separate from the ongoing
> development of new features.
> 6. If it becomes necessary to distinguish versions built with .Net 1.1 and
> .Net 2.0, we'll do so. But at the moment, there seems to be no need.
> That's how it looks now, anyway.
> Charlie
> -------------------------------------------------------
> This email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> _______________________________________________
> nunit-developer mailing list
> nunit-developer at
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at

More information about the Mono-devel-list mailing list