Skip to content
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.

Guidelines to Debug BlazorClient #79

Open
Sen-Gupta opened this issue Jan 27, 2022 · 4 comments
Open

Guidelines to Debug BlazorClient #79

Sen-Gupta opened this issue Jan 27, 2022 · 4 comments

Comments

@Sen-Gupta
Copy link

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
Copy link
Author

We are on VS 17.1.0 Preview 3.0!

@amolenk
Copy link
Collaborator

amolenk commented May 27, 2022

Is this still a problem with VS 2022?

@Sen-Gupta
Copy link
Author

@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

@amolenk
Copy link
Collaborator

amolenk commented Aug 9, 2022

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: dotnet/aspnetcore#22092

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants