I recently had my PC replaced, and now my new machine won't run our C++ unit tests that are targeting .NET 3.5. I have VS2010 + SP1Rel installed. And I've followed the additional configuration steps listed here: http://msdn.microsoft.com/library/gg601487.aspx#re-targeting35AdditionalSteps
I'm still unable to run the unit tests, even though the same tests ran on my old PC (which also had VS2010 + SP1Rel installed). I get the following errors when I try to run the unit tests in the IDE and via the VS2010 command prompt, where my local machine name is [xxx]:
Warning 10/10/2011 4:52:25 PM Failed to queue tests for test run '[xxx] 2011-10-10 16:52:25' on agent [xxx]: Object of type 'System.Runtime.Serialization.TypeLoadExceptionHolder' cannot be converted to type 'System.Collections.Generic.Dictionary`2[System.Uri,Microsoft.VisualStudio.TestTools.Common.AgentRuleDataCollector]'.
Warning 10/10/2011 4:52:25 PM Test run '[xxx] 2011-10-10 16:52:25' could not be executed. No agents are marked online to execute test run.
I am able to run the unit tests if I use the VS2008 command prompt, but that is really inconvenient and I'd like to be able to run the tests from the IDE.
There was a connect issue opened here for the beta version, but it was marked not reproducable and has no workaround:
Most of the other posts I've seen have found no resolution, and most people have given up. Has anyone ran into this issue and found a resolution?
- Edited by lbarb Monday, October 10, 2011 10:25 PM typo
FWIW we are facing the exact same issue with handful of our developers Most are able to run our mstest unit tests that target .net 3.5 I thought it might be an issue of VS 2010 premium vs ultimate, but some of the developers who have premium have no issues. We all have SP1 installed In fact, on one of the boxes that has this problem, I reinstalled VS2010 premium and SP1 with no issues, (verified that devenv.exe.config and mstest.exe.config were correctly modified to allow targeting .Net 3.5) but to no avail. I have enabled verbose logging in all the config files I could, but nothing stands out to indicate why the tests are failing. Any help would be appreciated, and I am willing to provide any dumps or logs requested. Please just show ask me for what you need
Sounds like you are both having a problem with SP1 not installing correctly,
Can i get you to file a bug on this so our test team can take a look?
Eagerly awaiting your response, as I try keep the horde of unit test-starved developers at bay
Hi did you receive a fix for this issue as i am experiencing the same problem; we have VS2010 ultimate with SP1 installed . This issue has only appeared on one machine.
Any help would be appreciated.
- Proposed as answer by Stanleyabcd Saturday, May 05, 2012 1:08 PM