Wacky VisualSvn Upgrade
I recently upgraded my TortoiseSVN installation to 1.5 and as a consequence needed to upgrade my Visual SVN install for visual studio to 1.5.1. I received an unexpected error when upgrading Visual SVN - it claimed it needed the Visual SVN 1.3.2 (currently installed) msi to install 1.5.1. This felt really lame and as I had no local copy was also obnoxious).
Visual SVN does not provide easy links to old versions of VisualSVN but they do provide access. Based on the download link for Visual SVN 1.5.1 I inferred the 1.3.2 link:
http://www.visualsvn.com/files/VisualSVN-1.5.1.msi
http://www.visualsvn.com/files/VisualSVN-1.3.2.msi
Also it looks like when I installed Visual SVN I did so directly from a firefox download I must have done twice as the installer claimed it was looking for VisualSVN-1.3.2[1].msi. When I passed it the downloaded file it claimed it was not the correct one so I renamed Visual-SVN-1.3.2[1].msi and the error went away.
There is a lot of strangeness with Visual SVN / Tortoise SVN. Another time when I upgraded to Tortoise SVN I had to shutdown Visual Studio, Outlook, and Firefox.
The VisualSVN Setup also spends a lot fo time “Updating Visual Studio settings” but as far as I can observe from the task manager does absolutely nothing but wait.
That along with the TortoiseSVN forced reboot makes the entire upgrade process for Tortoise/VisualSVN really obnoxious.
July 8th, 2008 at 12:16 pm
As far as TortoiseSVN is concerned, I find just killing the explorer.exe process and then restarting the process will do the trick.
July 8th, 2008 at 1:20 pm
Sometimes Windows Installer requires older msi for upgrade, probably when internal Windows Installer gets broken for some reason.
Btw, you can find download links for older VisualSVN versions on changes page:
http://www.visualsvn.com/visualsvn/changes/
On “Updating Visual Studio” stage VisualSVN installer runs devenv.exe with special parameters to rebuild Visual Studio internal caches. It takes a long time and cannot be improved.