Can't debug wasm project after update to VS 17.8.6

[appel1]

Describe the bug

When attempting to debug a browser showing about:blank appears and then goes away after a while and an error is shown in VS.

Seems like a VS issue but thought I should mention it here in case there's a known solution or workaround.

See https://developercommunity.visualstudio.com/t/Debug-of-Avalonia-WebAssembly-app-fails-/10576821

To Reproduce

Create a new avalonia xplay solution using sorbet new avalonia.xplat
Debug browser peojwct

Expected behavior

Successful debug as with 17.8.4

Environment

• OS: Windows 11
• Avalonia-Version: 11.0.7
• Same with both Edges and Chrome

[migubis]

We have observed a similar problem and found out that it is (in our case) connected with the usage of UseUrls. I have submitted it to Microsoft under
https://developercommunity.visualstudio.com/t/Debugging-does-not-work-when-UseUrls-is/10582270

My problem is not connected to Avalonia in any way, but I thought maybe it helps to share my findings.

[maxkatz6]

I will convert this issue to discussion, as it has a very chance of being caused by Avalonia.
But there still could be some workaround or useful links to share.

[mb-jp]

Any news on this? it's a big problem for me 😭

[maxkatz6]

You might try .NET 9 previews with preview Visual Studio.
I haven't tested, but if it was fixed in runtime, it should be available there.

[mb-jp]

I couldn't get it to work with .NET 9 previews and preview Visual Studio. 😟

[JW-CH]

Any update on this?

[DVaughan]

Today I updated VS to Version 17.10.0 Preview 7.0. The problem still persists. I realize this may be a VS issue, but would like to know if there is a work-around that someone is aware of to get the stock Avalonia web template to launch and attach to the browser. Some things I've tried that have not worked:

• Modified await dotnetRuntime.runMainAndExit to runMain
• Tried alternate URLs in launchSettings.json: "applicationUrl": "https://localhost:5001;http://localhost:5000",
• Changed csproj file TargetFramework from net7.0 to net8.0 (I had an issue with updating the webassembly workload unfortunately).