Closed danroth27 closed 4 months ago
We would need setup logs before investigating. Likely it uninstalled the the SDK first and then got to the error in the host later which likely resulted in the SDK folder not being empty. The files in use, there is nothing we can do and is completely in control of the OS. I advise not spending a lot of effort investigating this as uninstall is notoriously tricky wrt files in use.
We would need setup logs before investigating.
I'm happy to collect whatever you need. Any pointers on how to collect these logs?
I wonder if we have .NET processes that are not shutting down cleanly during development?
Related customer report: https://github.com/dotnet/core/issues/6389#issuecomment-871430141
Old issue triage: we've made improvements here and the host running can cause issues.
Repro steps:
dotnet new blazorserver -o BlazorApp
cd BlazorApp
dotnet watch
Expected result: SDK uninstalls cleanly
Actual result: