This isn't something the current plan for #3186 will deal with-it's tracking in-place upgrade. I think any effort to help clean up old broken uninstalls would be handled by a separate tool, if we go after it: The uninstall issue itself seems to not be present in recent SDKs, so it seems fixed although we don't know for sure what the original problem is. Do you happen to have logs for the unsinstalls? Otherwise, I don't see much we can do to address this and I will just close the issue. You can remove them, at least according to the version of the SDK that you have installed. Not sure why 2.1.0 and 2.1.2 were not removed. I think livarcocc's reply from earlier applies here: ![]() I tried installing and uninstalling SDK 2.1.302 which carries runtime 2.1.2 to see if there's some simple repro, but the uninstall removed the files as expected. Maybe you (or something-Visual Studio?) tried to uninstall it a while back and that had a bug, so now we don't have a record of it. ![]() Question now is why your machine has the 2.1.0/ 2.1.1/ 2.1.2 runtimes. I suppose, I can make same for 2.1.202 sdk ? (not present in previous uninstaller list screenshot)įrom the log files, you uninstalled these and they went fine: So, if you remove folder and you have cmd/powershell opened, the deletion is is not taken into account. NET Core (reflétant tous les global.json) :īase Path: C:\Program Files\dotnet\sdk\2.2.102\
0 Comments
Leave a Reply. |