Blazor templates shouldn't contain "inspectUri"

[ilonatommy]

Template created in CLI with dotnet new blazor -int Auto. VS instance 18.8.0 Canary [11828.296.main] opened with access to 11.0.0-preview.5.26277.119 dotnet and packages.

Clicking on GUI "https" launch button, the app doesn't start, dialog appears:

Can be fixed with removing "inspectUri" from lanunchSettings.json for the chosen profile:

      "https": {
        "commandName": "Project",
        "dotnetRunMessages": true,
        "launchBrowser": true,
        //"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
        "applicationUrl": "https://localhost:7296;http://localhost:5297",
        "environmentVariables": {
          "ASPNETCORE_ENVIRONMENT": "Development"
        }

Action:

• Make sure our templates do not ship with "inspectUri" in launchSettings.json.
• Release notes should mention inspectUri should be remvoed OR gateway could have a dummy API added for inspectUri to fix existing apps migrating to new debugger.
• Update the docs https://learn.microsoft.com/en-us/aspnet/core/blazor/debug?view=aspnetcore-10.0&tabs=visual-studio#app-configuration-prerequisites.

[github-actions]

Triage Summary

Area: area-blazor (issue is about Blazor project templates generated via dotnet new blazor -int Auto shipping inspectUri in launchSettings.json, causing VS launch failure)
Type: Bug (the default Blazor template produces a project that fails to launch from VS without manual editing of launchSettings.json)

Potential Duplicates

• None found

Generated by Triage Comment Reviewer for dotnet/aspnetcore for issue #67066 · sonnet46 408K · ◷