Re: NUnit Version Numbering

>-----Original Message-----
>From: Charlie Poole [mailto:cpoole@xxxxxxxxxxxxxxxxxxx]
>Sent: Sunday, December 11, 2005 10:43 PM
>To: ''Gert Driesen'', ''Charlie Poole'', ''Kamil Skalski''
>Cc: nunit-developer@xxxxxxxxxxxxxxxxxxxxx
>Subject: RE: [nunit-developer] NUnit Version Numbering
>
>Hi Gert,
>
>> Charlie, apart from the increased size of the installer, are there any
>> objections for
>> Including separate versions of NUnit built targeting each specific
>> supported
>> framework ?
>>
>> Meaning, you'd have an installer containing NUNit versions for:
>>
>> Microsoft .NET 1.0
>> Mono 1.0 profile / Microsoft .NET 1.1
>> Mono 2.0 profile / Microsoft .NET 2.0
>
>The main objection is that you need to know what version of NUnit to run,
>depending on what you're testing. That's particularly hard if you're using
>the GUI, and switching between applications.

True, but this is something you'll always need to know. Not everyone is 
interested in using the latest CLR.

Giving people the choice to run their tests in the CLR they're targeting
is very important (for something as crucial as unit tests).

Forcing users to upgrade to the latest .NET runtime is not a mistake we should 
ever make. This is one of the areas where open-source projects can really make 
a difference, as MS has decided otherwise (which is their good right ofcourse).

>Of course, it isn't that clean right now, since you have to modify either
>the config or the command line argument anyway. But with a long-term goal of
>running one copy of NUnit for everything, that sounds like a step I the
>wrong direction.

Only changing the config to specify the CLR version to target will ofcourse not 
allow you to ever take advantage of the features provided by a given CLR 
version.

Note: IMHO, the public API of NUnit should remain consistent for all different 
CLR versions.

>The other issue is that we'd need to improve our installation technology
>first. Doing what you suggest with a VS deployment project sounds pretty
>tough. We're working on that though.

For NDoc, we're doing exactly that.

Gert




-------------------------------------------------------
This SF.net 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!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click