Really love Rider, but we absolutely need a way to debug Blazor WASM and an update on the roadmap.Come on JetBrain - Should I go back to VS?.Any updates, plans or thoughts from JetBrains? Cant agree more with M, as Blazor WebAssembly is now considered production ready by Microsoft since May 2020.Having full support in Rider would be great for the future of Rider and blazor. Is there a way to prioritize this issue? I am past the phase of prototyping with blazor wsam and am convinced it is a best option for some use cases.The thread asked "Is blazor webassembly debugging going to be supported in 2020.2? or can you give a roadmap for blazor as it has been released and fully supported by microsoft." Many - if not dozens of - comments decried the lack of debugging functionality when compared to Visual Studio.įor example, comments in the thread included: Rider developers haven't been shy about letting JetBrains know how they feel, especially on the company's YouTrack site where there's a thread on Blazor WebAssembly Client-Side Debugging, started about a year ago. But it's a start! Please let us know about your experience with this new feature!"
NET 5.0 applications, there is no simultaneous debugging of server-side and client-side code, and no support for pages opened in a separate browser tab or window. "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. Hit breakpoints during app startup before the debug proxy is running.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)
