When you uninstall from control panel there will be some packages do get left behind. Some are packages that do not participate in package ref-counting – often those that we do not build. Some package may be left behind because uninstalling packages in Visual Studio. If a package fails, uninstall will move on to uninstall the next package. Some are just too essential for other products to uninstall like the .NET Framework and Visual C runtimes: of the vast number of installers that chain them, too few ref-count them to rely on that feature.
Whatever the cause, having components left behind will consume disk space and may cause troubles upgrading to Visual Studio RTM.
This is how we can completely removing Visual Studio components left behind after an uninstall.
Forcibly uninstall using original installer
You do not need to have a bundle installed to forcibly uninstall packages by default. If you have the original installer – say, a previous download – you can run it directly like so:
vs_enterprise.exe /uninstall /force
No comments:
Post a Comment