Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 0.16
-
Fix Version/s: 0.16
-
Component/s: Test Plugin
-
Labels:None
-
Environment:Windows
-
Number of attachments :
Description
When running nunit-console (version 2.2.8) from the command line on an NMaven project, I get the following error:
"Could not load file or assembly 'nunit.framework-2.2.8.0, Version=2.2.8.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified."
Everything runs fine with NUnit version 2.2.0.
Issue Links
- is depended upon by
-
NMAVEN-186
Integration test failures
-
Activity
Shane Isbell
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
Carlos Sanchez
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
Carlos Sanchez
made changes -
| Link |
This issue is depended upon by |
Brett Porter
made changes -
| Fix Version/s | 0.16 [ 14352 ] | |
| Affects Version/s | 0.16 [ 14352 ] |
Brett Porter
made changes -
| Component/s | Test Plugin [ 13429 ] |
Brett Porter
made changes -
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Assignee | Brett Porter [ brettporter ] | |
| Resolution | Fixed [ 1 ] |
The NUnit assembly for version 2.2.8 does not work with DotGNU, so I recompiled the source, sometime last year. This compile was under one of the old versions of NMaven that still embedded the version in the filename (and hence within the assembly Manifest). The Mono version of nunit-console was on my system path and did not mind that the assembly manifest name (with version attached) was different than the assembly file name. The non-Mono versions do mind and complain about not being able to load the assembly. I fixed this problem by putting a new NUnit 2.2.9 assembly into the trunk: this assembly's filename and name within the manifest match.