I\'m currently working in the Visual Studio 2012 RC with a test project. I have included the following assemblies:
This seems to be fixed in Visual Studio 2012 when it went RTM. No need to update config files
I've tested that in Visual Studio 2012 Update 4 and Visual Studio 2013 Update 1 RC and your code works flawlessly with the above mentioned code and assembly references and without updating the config file of the test runner. It is possible this was broken in a beta or release candidate of Visual Studio 2012, but if it was, it seems to be fixed now.
As Hans mentions you can update the .config
file for the vstest.executionengine.x86.exe.config
, but that changes the behavior for all test projects on your machine and needs to be applied to all people working on your project (and on a build server should you be using one). This should be a last resort!!