I missed two NUnit Releases!
I just learned that NUnit 2.2.4 was released on 14-Dec, and 2.2.3 nearly a month earlier. I’ve been running 2.2.2 forever; how shameful. It looks like they’ve finally fixed the annoying issues w/ running NUnit under multiple framework versions, and generally cleaned things up.
NANT 0.85 RC 3 won’t compile against NUnit 2.2.2 binaries (NUnit.Core.TestRunner is missing the FrameworkVersion property), so hopefully this will solve that issue as well. [UPDATE: It doesn't. RC 3 was released back in April of 05, so it can't be dependent upon NUnit 2.2.4. I'm moving to the latest nightly build, which I know from experience works].
UPDATE 2: I’m having the same problem using the 13-Dec-05 nightly build. I’ve built an earlier December nightly without problems on my home dev machine; what’s wrong now?
I’m getting this when building NAnt.NUnit2:
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2Task.cs(213,45): error CS0117: 'NUnit.Core.TestRunner' does not contain a definition for 'FrameworkVersion'
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2Task.cs(220,29): error CS0117: 'NUnit.Core.TestRunner' does not contain a definition for 'FrameworkVersion'
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2Task.cs(227,33): error CS0117: 'NUnit.Core.TestRunner' does not contain a definition for 'FrameworkVersion'
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2Task.cs(232,29): error CS0117: 'NUnit.Core.TestRunner' does not contain a definition for 'SetFilter'
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2TestDomain.cs(89,13): error CS0117: 'NUnit.Core.RemoteTestRunner' does not contain a definition for 'Out'
S:\scrap\nant-0.85-nightly-2005-12-13\src\NAnt.NUnit\NUnit2\NUnit2TestDomain.cs(90,13): error CS0117: 'NUnit.Core.RemoteTestRunner' does not contain a definition for 'Error'
Curiously, nant ships with precompiled NUnit DLLs in lib/net/1.1, and presumably in the folders for other implementations and versions of the framework as well. When VS loaded the solution, it wired up the references to the nunit DLLs to the NUnit 2.2.x DLLs which are registered in the GAC by the NUnit installer. I’m guessing from the failure above that nant relies on slightly modified NUnit source code!? That seems odd, but why else wouldn’t it work w/ the stock NUnit distribution?
Anyway, it’s building now; I just set the References Path for the Nant.NUnit2 project to include the lib\net\1.1 folder, which is where the dependent DLLs are located in the Nant source distribution. Now it builds.