Description
Is there an existing issue for this?
- I have searched the existing issues
Is your feature request related to a problem? Please describe the problem.
For a few weeks I've had a completely broken hot reload in razor pages. Any change anywhere in the projects would need a full recompilation of the web project. Today was the day I was tired enough of it and said "let's get to the bottom of this".
All of a sudden, I stumbled upon #41645. Checked my verbose logging, apparently I had the same exact problem in my project - something for some reason added the AdditionalFiles directive for one of my files. Removed it and it's back to working state.
The same is reported in Razor repository (last comment is the solution), though it's about Blazor. Not sure which repo is the target for this issue.
Describe the solution you'd like
The point of this issue is not that the fix is needed for such duplicate (as it's clear from #41645 it's not exactly worth expecting to cover every single edge case to work), but rather a wish for the watcher to be more loud. Right now, the warning is hidden behind verbose logging, which is quite counter productive.
Why is the warning just a verbose level? Can anything be done about this so warnings are visible in the output of default logger? It would have saved quite some time in my case.
Additional context
No response