Cannot hit breakpoint when Blazor wasm project path contains special characters

[laiwang233]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

This problem occurs when the created project path contains the # character

Expected Behavior

Hit breakpoint

Steps To Reproduce

Create a Blazor WASM project with the # character in the project path

Exceptions (if any)

No response

.NET Version

6.0.400

Anything else?

[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

This problem occurs when the created project path contains the # character

Expected Behavior

Hit breakpoint

Steps To Reproduce

Create a Blazor WASM project with the # character in the project path

Exceptions (if any)

No response

.NET Version

6.0.400

Anything else?

Author:	fzh233
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[thaystg]

@lewing this is fixed on .net7, do we want to backport?

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
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

This problem occurs when the created project path contains the # character

Expected Behavior

Hit breakpoint

Steps To Reproduce

Create a Blazor WASM project with the # character in the project path

Exceptions (if any)

No response

.NET Version

6.0.400

Anything else?

Author:	fzh233
Assignees:	thaystg
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[ChristianLindkvist]

I just upgraded my WASM-project to .net 7 and now I cannot hit breakpoints if there are special characters in the path. Doesnt seem fixed, it worked in .net 6. See attached image, if I set a breakpoint I get a blank page and I can see weird characters when I hover the path.

Note: we use swedish characters throughout the codebase.
I got this error and if I renamed the file so that it didnt contain any "special" characters - then it worked fine.