aspnetcore: BlazorWasmDebuggingExtension cannot find 'Microsoft.AspNetCore.App' version '5.0.0'
Moved from https://github.com/OmniSharp/omnisharp-vscode/issues/4489#issuecomment-816899280
There seems to be problems with the new Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension. I have dotnet on the path, but it throws this error when trying to attach to a hosted Blazor Webassembly app.
Launching debugging proxy from /Users/nikolaiemildamm/.vscode/extensions/ms-dotnettools.blazorwasm-companion-1.0.0/BlazorDebugProxy/BrowserDebugHost.dll
ERROR: It was not possible to find any compatible framework version
The framework 'Microsoft.AspNetCore.App', version '5.0.0' was not found.
- No frameworks were found.
You can resolve the problem by installing the specified framework and/or SDK.
Here is proof dotnet is on the path with the required framework:
This is my launch configuration:
{
"version": "0.2.0",
"configurations": [
{
"name": "Launch and Debug Hosted Blazor WebAssembly App",
"type": "blazorwasm",
"request": "launch",
"hosted": true,
"preLaunchTask": "npm run build:debug",
"program": "${workspaceFolder}/src/Presentation/WebApp/Server/bin/Debug/net5.0/EcosystemMapGenerator.Presentation.WebApp.Server.dll",
"cwd": "${workspaceFolder}/src/Presentation/WebApp/Server"
}
]
}
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 33 (19 by maintainers)
AFAIK, the releases happen on an as-needed basis so I’ll have to follow-up to see how things are rolling there.
Thank you very much! Our team (and I’m sure many others) would appreciate an update.
Great to hear, I’ve been hitting this issue as well. Is there an estimate at all for the next release?
Yes, so about two months ago, we shipped an update to the debugging experience in Blazor. It introduced a new extension that was responsible for launching the debugging proxy on the user’s local machine and returning the host the debug proxy is running on.
This extension depended on another extension that would download the .NET runtime onto the users machine (since the debugging proxy needs it to run). Recently, there was a behavior change in the extension and it no longer installs the correct runtime, the launching of the debug proxy fails, and the extension returns back
undefinedas the host the extension is running on.I pushed a fallback for this but it will be fully shipped in the next release of the C# extension.
@captainsafia thanks, this lets me move the missing runtime manually as a fix until someone at the team gets this sorted 😃
I did this on MacOS by copying the
Microsoft.AspNetCore.Appruntime from:/usr/local/share/dotnet/shared/to:/Users/{yourUserName}/Library/Application Support/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/5.0.5/sharedHope this helps others having the same issue.
Also, the debugging experience seems much more stable from my initial tries. Nice work!
No, I get the same issue on Linux.
This issue should be resolved now with the latest version of the C# extension (v.1.23.12).
@lucaswalter We’re working on inserting a couple more changes before making a release. Conservatively, I’d say before the EoM.
On Linux I’m getting this now when debugging in VS Code.