This is what I\'m getting when I build my Test project:
With th
Leniel,
Thanks for raising this issue.
As we discussed here, it indicates that shadow copy is causing the problem.
Please ensure that the Microsoft.VisualStudio.TestPlatform.Core.dll
is loaded from its installation location %VSInstallDir%\Commmon7\IDE\CommonExtensions\Microsoft\TestWindow
path and not from a temporary path like %appData%\assembly\dl3\
that you are observing right now. This should fix the problem for you.
Also I wanted to update you that in the latest code, we have improved our logic and with the improved logic, it would not matter from where the binary is getting loaded and it would just work for you.
Regards
Aseem Bansal
One more point:
Environment.ExitCode = 0;
Needs to add to end of each test during its clean-up! I learned this hard way. MS unit test framework checks this, and not run next test with non-zero ExitCode from previous test!
This is a very good thread, I solve almost all my unit test issues in this thread.
Found a correlation:
When NuGet auto-pull is enabled, I run into this issue on VS 11 after about ~15 builds. Deleting the Packages folder and forcing a re-pull of dependencies on build corrects.
I also noticed that if I manually purge the obj/bin folders in the solution root, the solution is corrected.
Therefore, I am thinking this sounds like the Test Suite is not updating cached dlls with that of the current solution configuration. As we edit, the dlls are getting out of sync and thus causing the unit test fixture to fail to initiate.
Hope this helps.
I had this problem, I tried the suggestion in a comment by @chrisortman and it solved my problem.
He suggested deleting:
%appdata%\assembly\dl3
Although I found it here:
%appdata%..\..\Local\dl3
I was going mad. Truly mad.
Thanks Leniel and Aseem Bansal for you help.
I have similar problem, but solution with this post not help me, My VS 2012 + silk4net not load test in Test Explorer.
Before I removed Telerik Test Studio from my PC. But extension for VS not removed. After I removed this extensions started to work correctly. Who see the problem persists, please view extension may be a problem in them.
Hope this helps.