I am using Visual Studio 2022 for Blazor WebAssembly Project and the ASP.NET Core API Project. When I run these projects independently, they works fine in Edge, Chrome browsers but, when I select Multiple-Startup projects, I am getting the following error.
One or more errors occurred.
Failed to launch debug adapter. Additional information may be available in the output window.
I had the same issue with Visual Studio 2022. I could solve the issue by disabling the script debugging in the drop-down of green arrow where we run the project. Please see the following screenshot.
I had this issue until I removed this line from launchsettings.json under profiles on the server side code.
Failed to launch debug adapter Unable to launch browser...
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
One working tweek is disabling JavaScript debugging in either of these two ways:
Finally..... I resolved by modifying Tools-->Options-->Debugging--->General and enabling following two checkboxes as shown in image
For me, just closing the browser solved it.
I solved this problem by setting the config "launchBrowser": false for the current profile in the file Properties/launchSettings.json.
It seems there is a browser launch problem. This may be caused by rights issues.
Try to stop the site in the IISExpress background process in the system tray of the target project. Then exit the IISExpress background process itself.
Refer to this article:
On a related note, I encountered this error message after cloning the first Blazor project I'd worked on in VS 2022.
It turned out that I hadn't installed all the build tools required for the (WebAssembly) Blazor project.
Go to Tools \ Get Tools and Features... then the Individual Components tab.
After adding .NET 6.0 WebAssembly Build Tools and .NET WebAssembly Build Tools I was able to successfully debug the project.
I run into this issue because of powershell restrict mode.
Cannot dot-source this command because it was defined in a different language mode. To invoke this command without importing its contents, omit the '.' operator.
I solve it by the following steps.
deleting the VSDBG debugger folder located at "%USERPROFILE%\vsdbg\vs2017u5" may help resolve the issue. Once you have deleted this folder, you can restart the debugger by pressing F5. Doing so will trigger the automatic recreation of the VSDBG debugger.
For further information on debug properties, you may want to consult Microsoft's official documentation, which can be found at https://learn.microsoft.com/en-us/visualstudio/containers/container-msbuild-properties?view=vs-2022. This documentation covers the use of various properties in MSBuild files to control the behavior of the debugger in containerized environments.
I wanted to see more info about some Exceptions that my app was raising, so I ticked the following setting in the VS Launch Profiles dialog. But once I'd ticked this I started getting the "Failed to launch debug adapter" error when I tried to debug the app. So I unticked the setting again.
I was getting this error alongside the following error in the console:
Invalid value for NO_PROXY: ... (Expected values: "localhost" or "127.0.0.1")
Just like it is documented here, if your environment is using a proxy, then you need to add localhost to your NO_PROXY environment variables.
On Windows:
NO_PROXY to a value of localhost.For me, restarting all instances of Visual Studio worked.
in launchSettings.json, in profiles object set "jsWebView2Debugging": false, this resolved my issue
I had renamed my NodeJs folder in C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio as it conflicted with other NodeJS versions installed. By restoring it back to original state, this problem went away.
I started getting this error when attempting to debug a Static Web App, running behind the SWA CLI, with Visual Studio 2022. It had been working previously, so it's likely that some unknown update was responsible for the change in behaviour, but after hours of trying and failing to find the cause I hit upon this workaround.
In my case, the app's launchSettings.json had both a launchUrl and an applicationUrl setting:
"launchUrl": "http://localhost:4280",
"applicationUrl": "http://localhost:5080"
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
In this case, the {url.port} placeholder in the inspectUri setting was expanding to the port specified in the launchUrl setting, i.e. 4280 - the port the SWA CLI was running on. Examining the visualstudio-js-debugger.txt file showed that this request was being refused. Changing it to explicitly use the port that the app was running on, i.e. 5080, fixed the problem for me.
"inspectUri": "{wsProtocol}://{url.hostname}:5080/_framework/debug/ws-proxy?browser={browserInspectUri}"
In my case, I got the same error message as the original post, but the Additional Information part indicated that EACCESS to the port for the debugger was denied. I fixed the issue by stopping and restarting the WINNAT service as follows.
net stop winnat
net start winnat
For me, the ridiculous problem was build profile being set on Release instead of Debug. It's worth a double-check.
I was able to resolve this issue by selecting a newer version of python in the debug properties. To do that, go to Debug>ProjectName Debug Properties>General. In that window select a newer python version next to Interpreter. In my case, Python 3.9 worked.
If no other python versions are displayed, you will have to install a newer version of python. I was making a console application and this is the only thing that worked.
© 2022 - 2024 — McMap. All rights reserved.