Blazor Debugging in VS Browser KeepAlive

[TanayParikh]

This issue is broken off into two parts:

1. aspnetcore-browser-refresh.js:55 Unknown payload: { "type" : "Ping" }
   • We're currently failing to handle the Ping message here
   • We need to handle this message somehow. We can do a simple no-op, however this may be a good opportunity to tackle Replace batch files with KVM #2
2. Running a Blazor web app doesn't always launch the browser
   • https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1613517#3285696
   • Essentially making a keepalive mechanism for the browser while debugging.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[softworkz]

aspnetcore-browser-refresh.js:55 Unknown payload: { "type" : "Ping" }

What's the status of this? (I cannot access the link)

I'm seeing this frequently when saving CSS files - in the most simple case: No Blazor, ASP.NetCore project serving static files only. VS 17.5.2, Microsoft.AspNetCore.App 6.0.15.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.