NUnit isn't running Visual Studio 2010 code

Question

I'm trying to load a Visual Studio 2010 beta dll into the NUnit GUI. I get a popup error.

This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. You may be attempting to load an assembly build with a later version of the CLR than the version under which NUnit is currently running.

How do I force an executable to run under .NET 4?

Is this question actually relates to VS 2010 or .NET 4 code? -- I am looking for a tool that allows me to run NUNIT tests on Visual Studio 2010, and this question was misleading. — Nicolas De Irisarri
– Nicolas De Irisarri, Commented Nov 17, 2010 at 16:55

Geoff Dalgas · Accepted Answer · 2011-02-17 22:05:34Z

132

I've downloaded the NUnit 2.5 source and opened the VS2008 solution in the VS2010 beta. Once the conversion finished I opened all the projects and changed the target framework setting for all the projects to ".NET Framework 4.0". I then built the solution without any errors. I can now use the NUnit GUI app to run tests built for .NET 4.0. I've not done exhaustive testing of this build so there may be problems, but for my purposes it works fine.

Update: It is not necessary to rebuild NUnit. I discovered that if you add the following to the relevant NUnit config file you can run a test dll built for .NET 4.0.

Under <configuration> add:

<startup>
  <supportedRuntime version="v4.0.30319" />
</startup>

and under <runtime> add:

<loadFromRemoteSources enabled="true" />

edited Feb 17, 2011 at 22:05

Geoff Dalgas

6,2066 gold badges44 silver badges59 bronze badges

answered May 31, 2009 at 16:37

Charles Cook

1,9991 gold badge16 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

mkmurray Over a year ago

Ok, the configuration updates make it work, but I had to use version="v4.0.21006" for my requiredRuntime tag.

Brad Irby Over a year ago

BTW, the default location of the config file is: C:\Program Files\NUnit 2.5.3\bin\net-2.0\nunit.exe.config Adding those options to the config worked for me.

Andreas Öhlund Over a year ago

Couldn't get this to work with the latest Nunit + .net4 RTM. I added the suggested entries to nunit-console.exe.config but I get: System.ArgumentException: The net-4.0 framework is not available Tried with the above versions + v4.0.30319 I'm running 2008 R2 x64

Lance Fisher Over a year ago

For the console runner, change the configs as mentioned, but using v4.0.30319 for the RTM version of .NET 4.0. Also, run it with this command line argument: /framework=4.0.30319

Kevin Crowell Over a year ago

I had luck using the command line option /framework:net-4.0.30319 instead of changing the config. This was helpful so I could control which applications used the 4.0 CLR and which did not.

|

pelazem · Accepted Answer · 2010-04-16 20:44:57Z

25

With .NET 4 being released, I used

<supportedRuntime version="v4.0.30319" />

in the NUnit 2.5.4 exe.config instead of requiredRuntime, and the loadFromRemoteResources tag as shown above and all worked well. Thanks!

answered Apr 16, 2010 at 20:44

pelazem

1,3821 gold badge11 silver badges13 bronze badges

Comments

darky · Accepted Answer · 2011-12-26 23:34:28Z

17

You don't have to modify any file

just open this file and everything will work just fine

C:\Program Files (x86)\NUnit 2.5.10\bin\net-2.0\nunit-x86.exe

answered Dec 26, 2011 at 23:34

darky

1711 silver badge2 bronze badges

2 Comments

Nigel Touch Over a year ago

Thank you - solved my case. Have to use x86 version of nunit for unit tests compiled x86. CLR version warnings were a red-herring. Using nunit 2.5.10.

gavin Over a year ago

Same here, somehow has to use x86 version

Cristian T · Accepted Answer · 2010-04-27 10:40:59Z

12

In NUnit 2.5.5 you can specify in the command line the option /framework=net-4.0 and it is compatible with the new assemblies generated with the release of the latest VS2010.

answered Apr 27, 2010 at 10:40

Cristian T

2,3213 gold badges26 silver badges46 bronze badges

3 Comments

Jason Short Over a year ago

I have never been able to get this to work. I have seen people use /framework:net-4.0.30319 and all sorts of other variations. Would be nice if they included the actual options on the site docs.

Roman Starkov Over a year ago

@Jason It appears that this only works on the console version. The GUI version doesn't have this option.

realMarkusSchmidt Over a year ago

+1 for mentioning that this works starting from version 2.5.5! I had NUnit throwing ArgumentExceptions and NullReferenceExceptions on one of my machines, and it turned out that it was because of version 2.5.0.

Scott Marlowe · Accepted Answer · 2010-06-30 12:53:35Z

2

The proposed solution worked great for getting NUnit to run. Unfortunately, when I then got to my code coverage step, NCover started giving me:

Profiled process terminated. Profiler connection not established.

The best solution I found to this was to just use the "-x86" version of NUnit with NCover:

NCover.Console.exe nunit-console-x86.exe --additional params--

Works now.

edited Jun 30, 2010 at 12:53

answered Feb 10, 2010 at 20:05

Scott Marlowe

8,03512 gold badges47 silver badges53 bronze badges

1 Comment

CubanX Over a year ago

Thank you for this, I was experiencing the same issue, your fix solved it!

Dan Paden · Accepted Answer · 2011-04-14 19:47:38Z

2

To find your .net 4 version from the Visual [C# 2010 Express, or which ever] go to the Visual application's "About" under the menu's Help item. It should show up as the version under the Microsoft .NET Framework line on the top right hand side of the window.

answered Apr 14, 2011 at 19:47

Dan Paden

211 bronze badge

Comments

Michael Sorens · Accepted Answer · 2011-01-21 04:23:59Z

1

I ran into the very same error message while running NUnit 2.4.8. As I had not upgraded in some time I installed the current NUnit (v2.5.9) and found that it now supports VS2010 assemblies. So if you have newly encountered this error check your NUnit version: as of December 2010 (or so) the only thing you need to do is upgrade NUnit.

answered Jan 21, 2011 at 4:23

Michael Sorens

37k26 gold badges120 silver badges175 bronze badges

1 Comment

DrLazer Over a year ago

i am running NUnit 2.5.9 downloaded on 15/03/2011 and this problem just wont go away for me. Even if i try the proposed solution

Crackerjack · Accepted Answer · 2011-06-03 17:23:27Z

1

As of NUnit 2.5.10 you can enable visual studio support in the GUI runner:

Tools-> Settings-> IDE Support

After that I was able to successfully attach to the nunit-agent.exe process which runs your assembly in a .NET 4.0 app domain

answered Jun 3, 2011 at 17:23

Crackerjack

2,1543 gold badges28 silver badges36 bronze badges

Comments

Adam · Accepted Answer · 2010-07-22 16:15:09Z

0

If you experience this issue after upgrading to nunit 2.5.5 then you will need to upgrade nant to the latest version for me it was .91 alpha.

answered Jul 22, 2010 at 16:15

Adam

1

Comments

Ernest Poletaev · Accepted Answer · 2011-05-26 10:21:52Z

0

I found usefull to start from NUnit Application Template. It support VS C# Express, allows debugging tests and contains precompiled NUnit for .NET 4.0. Thank to author new test project gets ready with one click.

answered May 26, 2011 at 10:21

Ernest Poletaev

6005 silver badges15 bronze badges

Collectives™ on Stack Overflow

NUnit isn't running Visual Studio 2010 code

10 Answers 10

9 Comments

Comments

2 Comments

3 Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

9 Comments

Comments

2 Comments

3 Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related