Blazor webassembly project Program.cs cannot be debugged

[HolyOne]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

In a webassembly project, Program.cs (Client Project) cannot be debugged in Visual Studio
I have no idea if the lines work or not.

There are existing issues that label this one fixed. But I am using the latest VS and .net version and I have this problem.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0.200-preview.23624.5

Anything else?

No response

[javiercn]

@HolyOne thanks for contacting us.

Are there any errors on the output console on the server, or on the dev tools in the browser?

[ghost]

Hi @HolyOne. 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.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

In a webassembly project, Program.cs (Client Project) cannot be debugged in Visual Studio
I have no idea if the lines work or not.

There are existing issues that label this one fixed. But I am using the latest VS and .net version and I have this problem.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0.200-preview.23624.5

Anything else?

No response

Author:	HolyOne
Assignees:	-
Labels:	untriaged, area-Debugger-mono
Milestone:	-

[HolyOne]

Today it is working :|
Sorry, I am sure I tried several times before but since the problem doesnt seem to happen now, i cant provide output console.

[tommcdon]

Possibly related to #98208
@thaystg

[tommcdon]

Sorry, I am sure I tried several times before but since the problem doesnt seem to happen now, i cant provide output console.

@HolyOne no worries at all! Please feel free to reach out again if this issue re-occurs. I'll close this issue for now until we have more details on the source of the problem.