Skip to content

Hot reload using dotnet watch doesn't work 98% of the time #40091

@chrissainty

Description

@chrissainty

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

My colleges and I use Macs and the .NET CLI for development. Our solution contains two Blazor Wasm hosted apps and a .NET Web API. There are 4 of us and in the past month only 2 of us have seen hot reload work and that was for a grand total of two days.

Running dotnet watch -v shows the following: watch : Hot reload capabilities: . which I'm sure I read somewhere is not a good sign?

I appreciate this isn't much to go on and I'd love to provide more information but I'm not sure what. But I'm happy to provide any other details.

Expected Behavior

Hot reload should work more than not.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0.101

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    ✔️ Resolution: DuplicateResolved as a duplicate of another issueStatus: Resolvedarea-blazorIncludes: Blazor, Razor Componentsarea-commandlinetoolsIncludes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPIfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyfeature-hot-reloadThis issue is related to the Hot Reload feaature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions