Closed deadcast2 closed 11 months ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Hi. Thanks for contacting us. We're closing this issue as there was not much community interest in this ask for quite a while now. You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.
Issue
I'm having a difficult time trying to get my new Blazor wasm project to utilize a hostname other than localhost. When I change the hostname the debugger suddenly stops working in Chrome (Version 92.0.4515.107). I've been able to reproduce this issue very easily with creating a new Blazor wasm project to test. I'm seeing an error saying "ProtocolException: Exception of type 'Microsoft.VisualStudio.Shared.VSCodeDebugProtocol.ProtocolException' was thrown." in my DebugAdapterHost-jsdebug.log file.
Reproduction
Also you should get this error in your DebugAdapterHost-jsdebug.log file:
My Visual Studio 2019 version is 16.10.4 and here are my installed package versions:
If you need anymore information from me please let me know. Thank you.