Hot reloading fails after the second change of a razor file #59027
Assignees
Labels
area-blazor
Includes: Blazor, Razor Components
feature-hot-reload
This issue is related to the Hot Reload feaature
Comments
dotnet-issue-labeler
bot
added
the
area-blazor
akorchev
changed the title
danroth27
added
the
feature-hot-reload
|
@tmat Is this a known issue? Also, in which repo should this be tracked? |
|
@akorchev Could you please run |
|
Here is the complete output until the error: |
|
@danroth27 wrote
There are a number of similar issues open in the SDK repo. |
@willdean Can you share the issue links? |
|
Here's mine which doesn't sound exactly like the above, but people have added comments that do: Here's another which is more like mine: dotnet/sdk#44910 Here;'s one which references Blazor: dotnet/sdk#44384 |
|
Looks like this is a general problem when the WASM runtime is not loaded yet when dotnet-watch tries to connect to the browser: Doesn't seem like a regression. I don't think this ever worked reliably. Will need to figure out what to do about it. |
|
I am also having this issue and I find it interesting that your terminal shows "building..." on app start, mine doesn't. |
|
Here are a few more tests that I conducted. .NET 8 Blazor app with Auto interactivityI tested an existing .NET 8 app created long before installing .NET 9 ( Adding a global.json with the following content solves the problem completely: I can update Home.razor many times and the error does not appear. .NET 9 Blazor app with Server interactivityI then created a server interactivity app to eliminate issues related to WASM runtime loading. To do that I used .NET 9 Blazor app without interactivityThen I created a Blazor app without interactivity via Those tests made me think that:
For completeness purposes I tested on a different Mac with the same results. Also tried with different browsers - the results were the same. |
|
@tmat This issue also reproduces in the latest 10.0 Preview 1 SDK on Linux/Mac OS. We have a known issue [#3202] that has been fixed in the old 10.0 Preview 1 SDK version [detail info]. |
|
fwiw, I had similar issues on Ubuntu 20.04 using a .net 9 version I built from source several weeks ago. It happened on a Blazor project that does not use WASM, just Blazor Server with HTMX on the client. Kept running into "Change failed to apply (error code: '...')..." messages. I know Ubuntu 20 is not supported on dotnet 9, and thought maybe it's something just on my environment, but now I see that it's in other platforms as well |
I'm running Ubuntu 24.04 with the latest .NET 9.0 version and am facing the exact same issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
Making a change to a .razor file no longer applies consistently after upgrading to .NET 9. I am using macOS 15.0.1 on a MacBook Pro M1 (could be related).
Expected Behavior
All changes should be hot-reloaded, not just the first one. This used to work in .NET 8.
Steps To Reproduce
dotnet new blazor -int Auto -o Blazor9Autoin some directory (from command prompt).dotnet watch --project Blazor9Auto/Blazor9Auto.csprojThis should open the browser.Exceptions (if any)
Change failed to apply (error code: '00-00-00-00-00'). Further changes won't be applied to this process..NET Version
9.0.100
Anything else?
ASP.NET Core version:
9.0.0
The IDE (VS / VS Code/ VS4Mac) you're running on, and its version:
Tested with VS Code, vim. The editor doesn't seem to matter.
Include the output of dotnet --info:
The text was updated successfully, but these errors were encountered: