Hot Reload agent improvements by tmat · Pull Request #60030 · dotnet/aspnetcore (original) (raw)

I have many questions, mostly because I was not part of hot-reload before.
Thank you for your patience with me. @tmat

The agent in WASM needs to be built-in. This makes it difficult to make any changes to the protocol.

By protocol, you mean the shape of "delta" bytes, right ?

Is this PR or dotnet/sdk#44539 actually making protocol changes ?

If not, what is the last PR which made any changes to it ?

Which flow (repository) is responsible for version of that protocol runtime/SDK/aspnecore/VS/another ?

Do the recent changes support backward and forward compatibility of VS/SDK/runtime ?

For example, can old VS/SDK still talk to project with new runtime+blazor on protcol level ?

Could you please explain versioning dependency between VS and the rest of it in more detail ?

aim to reduce the amount of APIs/endpoints that cross this versioning boundary.

This is more or less transport level change, right ?

Does it break the transport from new IDE/dotnet-watch to old WASM projects ?

Can latest IDE/dotnet-watch transport to Net8 WASM app ? (Net8 is Long Term Support)

@javiercn why is hot reload Blazor WASM feature and not WASM runtime feature ? (non-blazor WASM app template)
Does devserver play role in hot reload ?