dotnet / dotnet/aspnetcore

Blazor Debugging in VS Browser KeepAlive

Open
#45,041 14 comments 9 reactions 0 assignees View on GitHub
area-blazor feature-blazor-debugging feature-hot-reload Pillar: Technical Debt Priority:3
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

This issue is broken off into two parts:

1. [aspnetcore-browser-refresh.js:55 Unknown payload: { "type" : "Ping" }](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1600112)
- We're currently failing to handle the `Ping` message [here](https://github.com/dotnet/sdk/blob/a95405c8c0c21481323322eb9c9e74ded6e98b63/src/BuiltInTools/BrowserRefresh/WebSocketScriptInjection.js#L44-L56)
- We need to handle this message somehow. We can do a simple no-op, however this may be a good opportunity to tackle #2
2. [Running a Blazor web app doesn't always launch the browser](https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1613517)
- https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1613517#3285696
- Essentially making a keepalive mechanism for the browser while debugging.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.