We use TortoiseSVN along with VisualSVN as our source code control system.
We heave *never* had a problem with TortoiseSVN before, and have even made donations in the past to support it - that's how happy we were with it.
As usual, every few months, a new version of Tortoise was released, and we upgraded to it as usual...
I didn't even think about what I was doing - I have updated Tortoise on so many occasions it was just a formality...
After performing the install, and consequently rebooting, I loaded up my project in VS 2008, and tried to look into the log for one of my files...
And what happened? This!
So, I upgraded from version 1.6 to 1.7, but all of a suddenly, anything in 1.6 is apparently too old to view!
So, how then do I see my history as everything IS in the version 1.6 format!
Sigh.
I decided to just carry on....
So, I made a raft of changes to my project over multiple files.
It hen built it and tidied up a bit, and thought - "Now is a good time to check in my code...", so I tried to run the SVN Commit.
Should have updated all modified files right? They should now be in 1.7 format?
Oh, if only it were that simple!
Here's what I get when I try to check in:
So, since upgrading, I can't access my source history, and I CAN'T CHECK IN ANY NEW CHANGES OR FILES!
Checking out the Tortoise SVN website (http://tortoisesvn.net/downloads.html) there is a big warning that if you are upgrading from version 1.6, you will have to run the installer twice!
Okay, so I tried this, and it made NO difference at all!
I'm now in the process of uninstalling and re-installing the 1.6 client...
You can find the older version at: sourceforge.net/projects/tortoisesvn/files
I am running Windows 7 (32-bit) with the latest updates and service packs.
This could just be me, a singular exception to the rule, however, I would seriously advise checking this out before you blindly upgrade - just in case it saves you some pain...
Hope this helps folks!
Mark
I'll definately try it on a test machine first
ReplyDelete