NullReferenceException in VisualStudioConverter.ConvertVSSolution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nunit-console |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
When invoking the console runner. Please see below for console output. The problematic solution file is attached.
-------
$>nunit-console AdamsClient.sln
NUnit-Console version 2.6.2.12296
Copyright (C) 2002-2012 Charlie Poole.
Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov.
Copyright (C) 2000-2002 Philip Craig.
All Rights Reserved.
Runtime Environment -
OS Version: Microsoft Windows NT 5.1.2600 Service Pack 3
CLR Version: 2.0.50727.3643 ( Net 3.5 )
Unhandled Exception:
System.
at NUnit.Util.
at NUnit.Util.
at NUnit.Util.
at NUnit.Util.
at NUnit.ConsoleRu
at NUnit.ConsoleRu
at NUnit.ConsoleRu
Changed in nunitv2: | |
status: | New → Triaged |
Changed in nunitv2: | |
importance: | Undecided → Wishlist |
affects: | nunitv2 → nunit-console |
I have just had the same problem.
In my case cause was one or more projects not having a Property element with a condition for one of the build configurations defined in the .sln file. NUnit tries to find a property matching each and every build configuration for each and every project that it wants to include, even if the sln file points at another configuration for the given build type.
It also seems that sometimes, if the default build configuration doesn't have any customised values it is not included in the proj file.