You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a .Net Framework 4.8 test project using mstest. I have installed MSTest.TestFramework 3.0.0 and MSTest.TestAdapter 3.0.0. I am using Visual Studio 2022. The tests will be run on a build server with VS 2017. When I try to run a test in my local visual studio it fails with this error:
[Error] An exception occurred while invoking executor 'executor://mstestadapter/v2': Could not load file or assembly 'Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
I would rather not introduce a whole ton of extra dependencies with a newer version of MSTest. I have version 3.0.0 working in a similar solution and same environments. Can someone point me to what this error is being caused by?
The text was updated successfully, but these errors were encountered:
For anyone else who ever has this issue I fixed i by installing Version 3.0.1 of MSTest. Reinstalling 3.0.0 didn't help for some reason but the small update did.
I have a .Net Framework 4.8 test project using mstest. I have installed MSTest.TestFramework 3.0.0 and MSTest.TestAdapter 3.0.0. I am using Visual Studio 2022. The tests will be run on a build server with VS 2017. When I try to run a test in my local visual studio it fails with this error:
[Error] An exception occurred while invoking executor 'executor://mstestadapter/v2': Could not load file or assembly 'Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
I would rather not introduce a whole ton of extra dependencies with a newer version of MSTest. I have version 3.0.0 working in a similar solution and same environments. Can someone point me to what this error is being caused by?
The text was updated successfully, but these errors were encountered: