Debugging Blazor Server running in a dev container (WSL)

[TalonZA]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

My company has remove all docker instances from all developer machines due to licensing costs.

We are limited to using docker on WSL for our development. I have been a massive advocate for Blazor in my organisation and now that I have developed my app, the organisation has asked me to containerize it and get it ready for cloud.

It was a HUGE surprise to find that debugging a container is not available for Blazor. My specific request is for Blazor Server, I know there is another request for Blazor WASM here #37565

This is vitally important for me else I need to consider removing the Blazor UI from my application and replacing it with something else.

Describe the solution you'd like

In Visual Studio, I'd like to be able to debug my application in WSL. When I run my application, my breakpoints need to work as it would when I am running locally. I know it works with other standard .net applications.

Additional context

No response

[mkArtakMSFT]

Thanks for detailed explanation of the value this will provide to your company. We'll take into consideration your input for .NET 10 planning.

[danroth27]

@TalonZA Can you please walk me through how you tried running and debugging your Blazor app in WSL?. I tried creating a default Blazor Web App with .NET 8 and VS2022 17.11 and running it in WSL using VS and I was able to debug without issue:

[dotnet-policy-service]

Hi @TalonZA. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.