"For now, there are certain limitations: it works only for. "The first glimpse of long-awaited client-side debugging for Blazor WebAssembly is here!" JetBrains said. The Rider EAP Build (source: JetBrains). Automatically rebuild the backend *Server* app of a hosted Blazor WebAssembly solution during debugging, for example by running the app with dotnet watch run.Debug in non-local scenarios (for example, Windows Subsystem for Linux (WSL) or Visual Studio Codespaces ).This includes breakpoints in Program.Main (Program.cs) and breakpoints in the OnInitialized lifecycle methods of components that are loaded by the first page requested from the app.
However, even with that said, Microsoft indicated developers can't: The latest Blazor WebAssembly debugging guidance from Microsoft, dated August 2020, revealed that developers can debug from within Visual Studio for Windows, Visual Studio for Mac and Visual Studio Code - but only with the support of recent Chromium-based web browsers (Edge and Chrome). While that release lagged behind the client-side component, Blazor Server, full-functioning debugging lagged even further. While it's a much-requested feature, such debugging has been slow to come to Blazor WebAssembly, which Microsoft debuted in May 2020 in v3.2.
NET IDE from JetBrains, starting with a new Early Access Program build. Client-side debugging of Blazor WebAssembly apps, a hot topic among developers, is being addressed in the Rider.
0 kommentar(er)
