nunit-console.exe can be made to work with .NET 4.5 if nunit-console.exe.config is modified like this:
<startup useLegacyV2RuntimeActivationPolicy="true">
<!-- Comment out the next line to force use of .NET 4.0 --> <supportedRuntime version="v4.0"/>
</startup>
or this:
<startup useLegacyV2RuntimeActivationPolicy="true">
<!-- Comment out the next line to force use of .NET 4.0 --> <supportedRuntime version="v4.0.30319"/>
</startup>
The output of command line test execution in that case is this:
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 6.1.7601 Service Pack 1
CLR Version: 4.0.30319.18063 ( Net 4.5 )
Without modifications to the console config file, the test hangs (and seems to use .NET 3.5 for execution):
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 6.1.7601 Service Pack 1
CLR Version: 2.0.50727.5477 ( Net 3.5 )
ProcessModel: Default DomainUsage: Single
Execution Runtime: net-3.5
.
My conclusion is that something within nunit.exe GUI program is done differently from the console, which would explain why ReSharper works (it's probably using console behind the scenes).
Is nunit.exe compilation somehow different from nunit-console.exe with respect to .NET framework?
nunit-console.exe can be made to work with .NET 4.5 if nunit-console. exe.config is modified like this:
<startup useLegacyV2Runt imeActivationPo licy="true" >
<supportedRun time version="v4.0"/>
<!-- Comment out the next line to force use of .NET 4.0 -->
</startup>
or this:
<startup useLegacyV2Runt imeActivationPo licy="true" >
<supportedRun time version= "v4.0.30319" />
<!-- Comment out the next line to force use of .NET 4.0 -->
</startup>
The output of command line test execution in that case is this:
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 6.1.7601 Service Pack 1
CLR Version: 4.0.30319.18063 ( Net 4.5 )
ProcessModel: Default DomainUsage: Single
Execution Runtime: net-4.5
.
Tests run: 1, Errors: 0, Failures: 0, Inconclusive: 0, Time: 1.2793066 seconds
Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
Without modifications to the console config file, the test hangs (and seems to use .NET 3.5 for execution):
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 6.1.7601 Service Pack 1
CLR Version: 2.0.50727.5477 ( Net 3.5 )
ProcessModel: Default DomainUsage: Single
Execution Runtime: net-3.5
.
My conclusion is that something within nunit.exe GUI program is done differently from the console, which would explain why ReSharper works (it's probably using console behind the scenes).
Is nunit.exe compilation somehow different from nunit-console.exe with respect to .NET framework?