Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hot reload doesn't work on F5 but works when run `dotnet watch`

See original GitHub issue

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

Hot reload doesn’t work on a simple ASP.NET 6 app, when I run it with F5. My launchSettings.json is configured like this:


    "Kestrel": {
      "commandName": "Project",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      },
      "hotReloadEnabled": true,
      "applicationUrl": "https://outvers:3422;http://outvers:3420"
    },

Whenever I do a simple change in the .cshtml file hot reload doesn’t work.

But if I run the app using the dotnet watch command, then it works as expected.

I see that the output of the dotnet watch command differs from F5.

F5 output:

'Buddy.OutversService.exe' (CoreCLR: clrhost): Loaded 'D:\Repos\Buddy.OutversService\OutversService\bin\Debug\net6.0\Buddy.OutversService.dll'. Symbols loaded.
...
Microsoft.Hosting.Lifetime: Information: Now listening on: https://[::]:3422
Microsoft.Hosting.Lifetime: Information: Now listening on: http://[::]:3420
Microsoft.Hosting.Lifetime: Information: Application started. Press Ctrl+C to shut down.
Microsoft.Hosting.Lifetime: Information: Hosting environment: Development
Microsoft.Hosting.Lifetime: Information: Content root path: D:\Repos\Buddy.OutversService\OutversService
The thread 0x9bd8 has exited with code 0 (0x0).
The thread 0xdeb8 has exited with code 0 (0x0).
The thread 0x6620 has exited with code 0 (0x0).
The thread 0xdae8 has exited with code 0 (0x0).
The thread 0xe22c has exited with code 0 (0x0).
The thread 0xa53c has exited with code 0 (0x0).
The thread 0x3230 has exited with code 0 (0x0).
The thread 0xd0a8 has exited with code 0 (0x0).
The thread 0xa618 has exited with code 0 (0x0).
The thread 0x7d18 has exited with code 0 (0x0).
The thread 0xd4b0 has exited with code 0 (0x0).
The program '[400] Buddy.OutversService.exe' has exited with code 4294967295 (0xffffffff).

dotnet watch output:

...
  OutversService -> D:\Repos\Buddy.OutversService\OutversService\bin\Debug\net6.0\Buddy.OutversService.dll
watch : Started
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://[::]:3422
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://[::]:3420
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: D:\Repos\Buddy.OutversService\OutversService
**watch : File changed: D:\Repos\Buddy.OutversService\OutversService\Pages\ConsentPage.cshtml.**
**watch : Hot reload of changes succeeded.**