Hot Reload Takes Nearly 45 Seconds to Update

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:It's more difficult to complete my work]
Please see attached. Hot Reload now works for me, but takes forever to update, nearly 45 seconds to be more precise.

---

Original Comments

Feedback Bot on 11/11/2021, 03:48 PM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.

---

Original Solutions

(no solutions)

[mkArtakMSFT]

@pranavkm I know that you've been looking into this already. Is there another issue to dupe this against?

[NTaylorMullen]

More reports:

• https://developercommunity.visualstudio.com/t/VS2022-with-Blazor-Server-project-is-ter/1584485

[Mercurial]

same for me its just not flawless yet... :(

[CommonLoon102]

This is a duplicate of dotnet/aspnetcore#32867.
Workaround can be found here:
https://developercommunity.visualstudio.com/t/Hot-Reload-in-VS-very-slow-but-fast-wit/1563649

[MichelJansson]

I have similar issue, but just a lot worse.

For a slightly complicated page (~450 lines of razor, a few loops etc.) hot-reload from VS2022 takes 2:30 (2 minutes and 30 seconds) of really hammering the CPU to apply changes, and after that the changes still does not get rendered, and I have to restart the app.

Using the suggested workaround using dotnet watch it "only" takes 50-80 seconds. But now it actually also renders the changes.

It's only this extreme for this particular page. For very simple pages it's working OK, and changes are applied within 10 seconds. I've tried to find if it's any particular code on this page that is "bad" by process of elimination, and I can't find any specific error but in-line loops just seems to absolutely kill the performance.

[Mike-E-angelo]

I do apologize for the confusion here. According to this comment, this should have been addressed in preview2? This was my understanding when I posted my last comment, which seems to have contributed to the issue being locked. 😇

But now it appears with subsequent updates that this is slated for .NET7, if I understand correctly. I am totally fine with this as long as it is being communicated correctly so that we're not operating under false impression/understanding. For instance, I wouldn't have posted my last comment on dotnet/aspnetcore#32867 as I was under the impression that a fix had already been checked in as per the previous comment (which I probably misunderstood).

In any case, please know that I for one truly appreciate all the effort being applied there with this task and the project as a whole. You are truly moving mountains over there. 🙏

[CommonLoon102]

Based on this PR, it is being backported to .NET 6.0.3:
dotnet/sdk#23419

It was told that it will come in VS 17.2 (see last comment in the PR linked above). I don't know the ETA for that. Even 17.1 is yet to be released.

[Mike-E-angelo]

Ahhhhh 17.2, not to be confused with 17.1 Preview 2, as I was doing. :) Thank you for the pointer and correction, @CommonLoon102.

[pranavkm]

@Mike-E-angelo 17.2 preview1 would ship the same day 17.1 ships (part way thru February 2022).

[CommonLoon102]

17.2 Preview 1 is out but it is still 40 seconds to do a "hot" reload.