eShopOnDapr icon indicating copy to clipboard operation
eShopOnDapr copied to clipboard

Published 20 hours ago • verified publisher icon dotnet-architecture

Guidelines to Debug BlazorClient

Open Sen-Gupta opened this issue 3 years ago • 4 comments

Hello Team,

We tried to run the solution and it loads perfectly from Visual Studio. We are able to debug most part of the solution except the BlazorClient.

Following is our observations while debugging BlazorClient, we cleaned and rebuilt the projects to ensure our code changes are reflected

  1. Can debug Program.cs
  2. Can not debug any razor components
  3. Created Partial Classes for razor components and tried to debug, did not work.

What we observed that the JavaScript debugger was never shown as one of the debugger?

Works in Program.cs debug

But did not work on razor files image

and we did not see JavaScript debugger

Sen-Gupta avatar Jan 27 '22 06:01 Sen-Gupta

We are on VS 17.1.0 Preview 3.0!

Sen-Gupta avatar Jan 27 '22 06:01 Sen-Gupta

Is this still a problem with VS 2022?

amolenk avatar May 27 '22 18:05 amolenk

@amolenk , I'm not sure if I'm missing something but I'm still unable to debug razor pages.

FYI. I'm on. image

Placed debug in the catalog.razor image

But it stays in "No symbols have been loaded for this document".

Where am I wrong? We can definitely debug blazor wasm projects

Sen-Gupta avatar Aug 08 '22 09:08 Sen-Gupta

Hi, I've never tried this personally, when I wrote the Blazor client I was running/debugging it in VS Code directly and I had only the backend services running in Docker.

I'm actually not sure it's even possible. I found this (older, VS2019) issue which states that it's not supported: https://github.com/dotnet/aspnetcore/issues/22092

amolenk avatar Aug 09 '22 17:08 amolenk