|
RE: NUnit Version Numbering: msg#00031windows.dotnet.nunit.devel
> -----Original Message----- > From: nunit-developer-admin@xxxxxxxxxxxxxxxxxxxxx > [mailto:nunit-developer-admin@xxxxxxxxxxxxxxxxxxxxx] On > Behalf Of Charlie Poole > Sent: zondag 11 december 2005 21:13 > To: 'Kamil Skalski' > Cc: nunit-developer@xxxxxxxxxxxxxxxxxxxxx > Subject: RE: [nunit-developer] NUnit Version Numbering > > Hi Kamil, > > > > NUnit built with 1.1 running under 1.1 > > > > This one of course is not able to execute 2.0 compiled tests: > > The format of the file 'VotingSystemTest' is invalid. > > Yes, this is the main problem that led me to create a new > build using 2.0. > Part of the NUnit community is developers with only basic > understanding of > how the framework works. They don't always understand the "of > course" part > of your statement and expect it to work magically. ;-) > > Some day, we'll fork a process to run under the proper CLR. > > > > NUnit built with 1.1 running under 2.0 using config file > > > > Success!! Ok, now I can see it works, but it needs tweaking > of config > > file. > > Yes, exactly. > > > > NUnit built with 1.1 running under 2.0 using > /framework:2.0.50727 > > > > I get a message, that I need to install Framework version 2.0.50727 > > (which of course I have already installed)... > > You need /framework:v2.0.50727 <== note the 'v'. I actually > don't know if > this works under Mono, but it does under windows - something > more for me to > check. > > > > > > > NUnit built with 2.0 running under 2.0 > > > > It works by default. > > > > > > > > If you'd like to pick a particular combination that does > not work for > > you, > > > we can go into the details. > > > > Now I can see your point. Thanks! > > > > I remember that on mono it was not sufficient to change the config > > file - it failed later during runtime, but it seems it was > just a mono > > bug. I will try to retest this on mono and probably file a bugreport > > in mono runtime. > > One thing I guess might be a problem is that I tried nunit-console > > compiled for 2.0 profile, but dlls from 1.1 profile, maybe > they didn't > > work well together. > > I'm pretty sure that won't work. > > Actually, your problems are an indication that we should > consider using a > different version, even if it works without it. It would make > it easier to > debug such situations. > > I'll think about this some more, before the 2.2.4 release. 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 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_id=7637&alloc_id=16865&op=click |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: NUnit Version Numbering: 00031, Charlie Poole |
|---|---|
| Next by Date: | RE: NUnit Version Numbering: 00031, Charlie Poole |
| Previous by Thread: | RE: NUnit Version Numberingi: 00031, Charlie Poole |
| Next by Thread: | RE: NUnit Version Numbering: 00031, Charlie Poole |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |