-
Notifications
You must be signed in to change notification settings - Fork 1.1k
dotnet watch crashes with "An unexpected error ocurred" #47392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@tmat @jasonmalinowski Looks like the IDE/watch is attempting to replace an additional document that the generator doesn't know about, so something has gotten out of sync. |
@rogihee Mentions the following steps: You can attach to dotnet-watch process or monitor for exception via procdump |
@tmat thanks, will have a go again. Nowadays I usually try to avoid using dotnet watch during most of my workflow, because it is finicky. And limit it to only frontend part of development of a (Blazor) feature. But as an experiment I now started when I began a new feature branch. That involved in this case copy-pasting 2 files to have a beginning of a new feature, quickly renaming it. Just doing stuff that will definitely not build. It was during this the exception was thrown. |
Would you mind elaborating? Does 9.0.200 feel better? |
With 9.0.100 it was unworkable because Razor Class Libraries were not included in the watch profile due to a bug. This was my first attempt again in 3 months to use it again, and bumped into this after 5 minutes. So I don't have much mileage yet. My colleague says it's definitely better but still sometimes crashing / not working. Mostly you @tmat did a ton of effort in 9.0.200, been following the changes. Me and my colleagues would REALLY love to have good solid, reliable dotnet watch with Hot Reload. I'll do my best to use it again in my daily workflow and try to reproduce issues or attach procdump when it crashes. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
While working on my program I was working on modifying some blazor components, nothing fancy: just copying a blazor component, modifying the name, changeing the type of a parameter.
When I looked at the dotnet watch log it has crashed.
dotnet info:
Exceptions (if any)
Further technical details
dotnet --info
The text was updated successfully, but these errors were encountered: