Describe what happened:
I can't start a debugger session (or whatever) unless I disable the plugin.
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Failed to load the dll from [c:\Users\anthony\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare\dotnet-3.1.1\host\fxr\3.1.1\hostfxr.dll], HRESULT: 0x800700C1
The library hostfxr.dll was found, but loading it from c:\Users\anthony\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare\dotnet-3.1.1\host\fxr\3.1.1\hostfxr.dll failed
- Installing .NET Core prerequisites might help resolve this problem.
http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
The program '[28676] testhost.exe' has exited with code -2147450750 (0x80008082).
What was your system configuration?
Product and Version [VS/VSCode]: VSCode 1.44.2
OS Version[macOS/Windows]: Windows 10 Pro 1909
Live Share Extension Version: 1.0.2104
Target Platform or Language [e.g. Node.js]: .NET Core SDK 3.1.201
Steps to Reproduce / Scenario:
More here: https://github.com/dotnet/core/issues/4557
Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Screenshots
If applicable, add screenshots to help explain your problem.
Thanks for reaching out. Can you give us logs for investigation? You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Adding @jramsay
I'm having the same problem.
What was your system configuration?
Product and Version [VS/VSCode]: VSCode 1.45.0
OS Version[macOS/Windows]: Windows 10 Pro 1909 (OS Build 18363.815)
Live Share Extension Version: Live Share Extension Pack v0.3.4
Target Platform or Language [e.g. Node.js]: .NET Core SDK 3.1.201
Me too. Disabling the extension allowed debugging to work.
Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: Failed to load the dll from [c:\Users\Anthony\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare\dotnet-3.1.1\host\fxr\3.1.1\hostfxr.dll], HRESULT: 0x800700C1
The library hostfxr.dll was found, but loading it from c:\Users\Anthony\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare\dotnet-3.1.1\host\fxr\3.1.1\hostfxr.dll failed
- Installing .NET Core prerequisites might help resolve this problem.
http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
. Please check the diagnostic logs for more information.
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.ThrowExceptionOnConnectionFailure(Int32 connTimeout)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources, String runSettings)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler)
What was your system configuration?
Product and Version [VS/VSCode]: VSCode 1.45.0
OS Version[macOS/Windows]: Windows 10 Pro 2004 (OS Build 19041.208)
Live Share Extension Version: Live Share Extension Pack v0.3.4
Target Platform or Language [e.g. Node.js]: .NET Core SDK 3.1.201
Is there any update on this issue? LiveShare is pretty prominent feature of VS and vscode and it kind of sucks to have to keep it disabled.
@divinebovine, @AnthonyMastrean, @atruskie: thanks for reporting the issue! This should be fixed in our latest Live Share update available in the VS Code Marketplace (v 1.0.2236). If you can test your repro on the latest extension and confirm it is resolved it would be much appreciated.
@jramsay looks like its working for me! Thank you!
@divinebovine: thanks for confirming! Will close out this issue.
Most helpful comment
@jramsay looks like its working for me! Thank you!