StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONUnit assembly not found
text
Body
copied!<p>I've used NUnit before, but not in a while, and never on this machine. I unzipped version 2.4.8 under Program Files, and I keep getting this error when trying to load my tests.</p> <blockquote> <p>Could not load file or assembly 'nunit.framework, Version=2.4.8.0, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77' or one of its dependencies. The system cannot find the file specified**</p> </blockquote> <p>In order to simplify the problem, I've compiled the most basic possible test file.</p> <pre><code>using NUnit.Framework; namespace test { [TestFixture] public class Tester { [Test] public void ATest() { Assert.IsTrue( false, "At least the test ran!" ); } } } </code></pre> <p>I've added "C:\Program Files\NUnit-2.4.8-net-2.0\bin" to my PATH (and rebooted). Note that if I copy the test assembly into that folder, then</p> <pre> C:\Program Files\NUnit-2.4.8-net-2.0\bin>nunit-console test.dll </pre> <p>works, but</p> <pre> C:\Program Files\NUnit-2.4.8-net-2.0\bin>nunit-console c:\dev\nunit_test\test.dll </pre> <p>and</p> <pre> C:\dev\nunit_test>nunit_console test.dll </pre> <p>fail with the above error.</p> <p>Presumably I could get around this by copying the NUnit.Framework dll into my project's bin folder, but I don't remember having to do this in the past. Moreover, I get the same error in the GUI. Shouldn't the GUI know where the framework is located (that is, in the same folder)?</p> <p>@Scott, I'm not using Visual Studio. I use the following line to compile the test project.</p> <pre> %windir%\Microsoft.NET\Framework\v2.0.50727\csc.exe /r:"C:\Program Files\NUnit-2.4.8-net-2.0\bin\nunit.framework.dll" /t:library /out:test.dll test.cs </pre> <p>@devio, I tried both the msi and the zip with the same result.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload