0

I started the install of the VisualSvn plug-in for Visual Studio before I realized that Tortoise SVN is a pre-req. I clicked the Cancel button, but I received the "Install Successful" dialog for VisualSvn anyway. However, when I started Visual Studio, the VisualSVN item is not on the menu bar. When I view Visual Studio Extensions and Updates, I don't see VisualSvn in the list. The kicker is that when I try and re-install VisualSvn, I cannot because Visual Studio does not appear as an app I can install VisualSvn on.

So, it seems VisualSvn is half-in/half out. Is there a way to make the VSIX installer forget and allow me to re-install VisualSvn over the top of what's already there?

p.s. I tried to restore my machine to a point immediately before the interrupted install, but a such a restore point is not available

VA systems engineer
  • 2,856
  • 2
  • 14
  • 38
  • what's your VS version? I tested it in my VS community 2017 and go to Extensions and Updates-Online to search and install this extension, the installation is successful like this: https://1drv.ms/u/s!Atv5QNuFrncKmCo3n3GCOhQ4nh5Y – Sara Liu - MSFT Mar 08 '18 at 09:19
  • VS 2017 Pro. The problem is that I tried to cancel the install after I started the install (see description above) – VA systems engineer Mar 08 '18 at 12:09

1 Answers1

1

Usually we can also uninstall the extension from the command line using the VSIXInstaller.exe, I tried to the %temp% folder and find the installation log (VSIXInstaller_xxxxx) of this extension: VisualSVN for Visual Studio 2017 to check the Identifier Id, then use the following command to manually uninstall this extension:

vsixinstaller.exe /skuName:Pro /skuVersion:15.0.27130.2036 /u:VisualSVN.7D0F87F6-4A55-4C12-A903-998CF2ADFFE6

The extension be uninstalled successfully as below: enter image description here

Sara Liu - MSFT
  • 6,007
  • 1
  • 21
  • 27
  • Thank-you, the approach you suggested worked. I was able to uninstall VisualSVN successfully One difference: In my log file, I did not see the `skuname` or `skuversion` for Visual Studio, so I used this command with the VisualSVN Identifier I found in my log file: `vsixinstaller.exe /u:VisualSVN.7D0F87F6-4A55-4C12-A903-998CF2ADFFE6` – VA systems engineer Mar 10 '18 at 12:19