Reputation: 91
I just started with VisualSVN and got things messed up. I get complaints about working copies being too old (1.6). I have 1.7 TortoiseSVN and VisualSVN 2.5.5 and have tried many things but nothing helps.
So, I just want to start over, but the option "Add Solution to Subversion" is disabled in Visual Studio 2010. I tried deleting the repository in VisualSVN Server Manager, and uninstalled/re-installed VisualSVN. But the option remains disabled.
What can I do to just start over?
Upvotes: 1
Views: 629
Reputation: 30662
It's really strange you have an issue with that. You can simply upgrade your working copy either through Visual Studio | VisualSVN | Upgrade Working Copy (if you use VisualSVN) or through TortoiseSVN.
Please note that the question is completely irrelevant to the server side and is only about upgrading working copy format.
BTW you can always checkout a fresh working copy.
Upvotes: 0
Reputation: 7032
There was a major change in the way metadata is organized between 1.6 and 1.7, on the client side only. So 1.6 and 1.7 can talk to the same repositories, but the can not use the same working copies.
By the sounds of it, your problem with the error message would be sorted out by pulling the working copies again using your 1.7 tools. However, I'm not sure the interop with VS will, so you could also go back to a 1.6 client install. You'll certainly want to make sure that all clients on your system are 1.6 or 1.7, not a mix.
Upvotes: 0