[Feature]: Application Hot Reload

[WhitWaldo]

Visual Studio 2022 has been officially announced. One of the features cited in the release will be support for .NET Hot Reload and is further described as "you'll be able to use .NET Hot Reload to apply code changes without needing to restart or lose the app state."

That sounds awfully neat and similar to the refresh support announced back in 5.5. Of course, this still only supports 1-node clusters, but provided edit/refresh for ASP.NET Core services.

It'd be great to see an update to this support to allow for Hot Reload for all .NET service types and across 5-node clusters since this provides an even faster local development experience than the existing refresh application mode.

Describe the solution you'd like
Hot Reload is described in this presentation by Daniel Roth demonstrating Hot Reload in a Blazor app as having the file saved, IL diff detects what needs to change and then inserts the change into the running app without restarting. This means it's faster than an edit/refresh and means that the app doesn't have to be completely re-deployed to use it (e.g. all the state is exactly the same and doesn't have to be re-entered) for some scenarios. But as you can see at 40:36, it supports a fallback to a full refresh when something happens that can't be supported by the Hot Refresh.

Describe alternatives you've considered
N/A

Area/Component:
Development tooling

Expected behavior
N/A

Additional context
N/A

Service Fabric Runtime Version:
8.0+

Environment:
Local dev cluster

---

Assignees: /cc @microsoft/service-fabric-triage

[juho-hanhimaki]

Love the idea.

[WhitWaldo]

@sukanyamsft Now that VS 2022 released today and Hot Reload is officially supported with that release, is there any potential updates on the SF side in terms of supporting it for vastly faster local development of SF apps?

[akoni50]

+1, currently workflow is to delete and redeploy. Time-consuming process.