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.

[ghost]

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.

[ghost]

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.

[ghost]

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.

[kzu]

I can repro this even without debugging, for a new blazor web app template, while changing the app.css.

[BachiMjavanadze]

the same issue for me:

when I change the CSS this error occurs. even if I just don't add a new class, but just add an empty line at the end of the CSS script, this error occurs

[portal7]

Same here

[Duke4848]

I made a mistake and updated VS and getting the same issue now.

[cytoph]

I don't know if it makes sense to decrease the priority of this issue. The error message itself is only inconvenient, yes, but the failed call seems to mean that Visual Studio is unable to "push" the new version of the CSS file one has just saved - and that is contrary to how isolated CSS files (= per .razor file) work, as those get correctly "pushed" to the running site on save.

[RobTF]

It's just wrong - saving a CSS file shouldn't send a Ping, judging by the code in the JS file it should send an UpdateStaticFile.

I get this every time I save app.css in a Blazor standalone WASM app when debugging using VS. If I forego the debugger and run "dotnet watch" things work fine.

This is not just an inconvenience in the sense the error can be ignored - this is blocking hot reload, at least for CSS. It should be a priority to be fixed.

[lnaie]

In a pure wasm project (boot up from index.html, in just one project, not Project + Project.Client), I'm seeing this after I changed a style in the page's local css (e.g. Page.razor.css) and saved the file. Do we have a regression?

Can we also make the wasm hot-reload work with Aspire as well?

[softworkz]

I also do not understand the depriorization.

This is a BUG - Please fix!