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
Tests fail with "Could not load file or assembly 'Microsoft.VisualStudio.Shell.Interop" when PowerShell tools are installed and you use Microsoft.VisualStudio.Shell.Interop
#692
Message: System.IO.FileNotFoundException : Could not load file or assembly 'Microsoft.VisualStudio.Shell.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
We use this assembly in our tests, however, the binary lives alongside our tests - and before upgrading to xUnit 2.2 there was no issues loading it.
This only occurs when the PowerShell tools are installed.
If I start debugging and break on exceptions, I notice that this assembly initially fails to load while RockSteady is walking the types of file:///C:/PROGRAM%20FILES%20(X86)/MICROSOFT%20VISUAL%20STUDIO/2017/ENTERPRISE/COMMON7/IDE/EXTENSIONS/XSNRCEZZ.I1M/PowerShellTools.TestAdapter.dll. Stack below under Details:
CLR caches assembly failed loads - so I'm guessing whatever resolver is hooked up during the test runners never gets called back because it failed to load initially while trying to find TestExtensions.
This only occurred after upgrading to 2.2 - does this path only occur the first time Test Explorer sees an extension perhaps? I don't know why it didn't occur with xUnit 2.1.
After upgrading to xUnit 2.2, every VS test over in http://github.com/dotnet/project-system is failing with:
We use this assembly in our tests, however, the binary lives alongside our tests - and before upgrading to xUnit 2.2 there was no issues loading it.
The code in particular this branch: https://github.com/basoundr/roslyn-project-system/tree/MoveXunit.
The text was updated successfully, but these errors were encountered: