Seems that the "Restart Visual Studio command" does not wait for the VSIX installer prompt when there are pending installs/uninstalls.
It just starts VS and while the VSIX installer runs in the background waiting to be able to write to the now locked folders and files (I assume?!!!). Would not have expected that, but maybe the VSIX installer needs an ice-cold start and Restart don't do that?
Created some havoc in my list of extensions, as suddenly the (what's their name?) Package Collection installers wouldn't uninstall their list of extensions only it self (Or rather it disabled it self, and when I then uninstalled the Package Collection Title? it only uninstalled itself)Edit: Ups,- found out by experiment that extension pack installers don't uninstall their included extensions! ( That's terrible news for us extension hoarders 😱😁)
System:
Microsoft Visual Studio Community 2022 (64-bit) - Version 17.4.0 Preview 1.0
Seems that the "Restart Visual Studio command" does not wait for the VSIX installer prompt when there are pending installs/uninstalls. It just starts VS and while the VSIX installer runs in the background waiting to be able to write to the now locked folders and files (I assume?!!!). Would not have expected that, but maybe the VSIX installer needs an ice-cold start and
Restartdon't do that?Created some havoc in my list of extensions, as suddenly the (what's their name?) Package Collection installers wouldn't uninstall their list of extensions only it self (Or rather it disabled it self, and when I then uninstalled the Package Collection Title? it only uninstalled itself)Edit: Ups,- found out by experiment that extension pack installers don't uninstall their included extensions! ( That's terrible news for us extension hoarders 😱😁)System: Microsoft Visual Studio Community 2022 (64-bit) - Version 17.4.0 Preview 1.0
Windows 10 - 64 bit