Skip to content

'Failed to launch debug adapter' error running new .NET 6 project in IIS Express #31532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
NeoXtreem opened this issue Apr 4, 2021 · 4 comments
Closed

'Failed to launch debug adapter' error running new .NET 6 project in IIS Express #31532

NeoXtreem opened this issue Apr 4, 2021 · 4 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved

Comments

@NeoXtreem
Copy link

I have created a new Blazor WebAssembly App targeting .NET 6. When I run using the default IIS Express profile, a blank Chrome window is displayed, then the following error message appears after a short while:
image

This appears to be a known issue, and I've tried all the relevant suggestions described in this comment (by a Microsoft employee), namely disabling 'Script Debugging' (it was already disabled), and enabling the "new debugger", but to no avail.

I am using VS Community 2019 Preview (16.10.00 Preview 1.0), and .NET 6.0.100-preview.2.21155.3.

I created an identical new project targeting .NET 5, and I don't get this problem.
@ghost
Copy link

ghost commented Apr 4, 2021

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@pranavkm pranavkm transferred this issue from dotnet/sdk Apr 5, 2021
@captainsafia
Copy link
Member

@NeoXtreem It looks like you're running into a dupe of #30917.

We'll be shipping a fix in preview4. In the meantime, you can run your app in Development using Kestrel.

@captainsafia captainsafia added ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. area-blazor Includes: Blazor, Razor Components feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps labels Apr 5, 2021
@ghost ghost added the Status: Resolved label Apr 5, 2021
@NeoXtreem
Copy link
Author

@NeoXtreem It looks like you're running into a dupe of #30917.

We'll be shipping a fix in preview4. In the meantime, you can run your app in Development using Kestrel.

OK, thanks. Will do.

@ghost
Copy link

ghost commented Apr 6, 2021

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.

@ghost ghost closed this as completed Apr 6, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 6, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-debugging This issue is related to debugging of Blazor WebAssembly apps ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@captainsafia @NeoXtreem