views:

488

answers:

3

I'd like to try out a feature of AnkhSVN (namely, integration with Red Gate SQL Changeset tool) without doing an complete uninstall of VisualSVN. It feels dodgy, so I wanted to see if anyone else had experience that would either alleviate or confirm my fears.

Update
So I tried uninstalling VisualSVN and dropping in Ankh. As far as working within VSS itself, the change was completely transparent. Sadly, SQLChangeset did not work with this plugin, so that part of it was in vain.

Switching back was also painless, even to the point of not having to re-enter my license. So, good knowledge but no joy on the long-term goal.

+1  A: 

I haven't tried it, but I know Visual Studio supports multiple source control plugins. You just pick which one is active from the options by choosing Tools->Options from the menu and then finding the Source Control->Plug-in Selection page in the tree control on the left side of the window that opens.

It should just be a matter of installing Ankh and selecting it there for your tests, then setting back to VisualSVN when done. Of course, that assumes everything plays nice together.

Joel Coehoorn
I was sort of thinking the same thing, Joel; except VisualSVN isn't a SCCI compliant (a term I only learned today) source control plug in and as such doesn't show up in the list. But I figure that uninstalling AnkhSVN is the fall back position if things go blooey.
KevDog
If it's non-compliant, you might try doing your test in a VM. I wouldn't trust something not to break if you tried to have both active at once.
Joel Coehoorn
+1  A: 

You might be able to turn off / disable VisualSvn in Tools -> Addin Manager, and then select AnkhSvn as the current SCC Provider.

Can you describe how this changeset tool works, and how that should integrate with AnkhSvn?

Sander Rijken
The tool comes with SQLToolbelt, I'm not sure if they are selling it separately or if it comes bundled with SQLCompare. You use SQLCompare to generate a DB script and SQLChangeset tracks that and adds it to your VCS repository. TFS is supported out of the box, but other solutions require a compliant plug-in.
KevDog
Any idea what it takes to be a compliant plug-in? Do they expect an Scc Provider, or do they talk to the (old) MSSCCI api?
Sander Rijken
I believe the hook is the MSSCCI api. I think that TFS uses this API also.
KevDog
+1  A: 

Yes. I've been able to run VisualSVN and AnkhSVN on Visual Studio at the same time. One thing to note is that you won't be able to use both at the same time. VisualSVN is an add-in, while AnkhSVN is truly a source control plugin. To use one or the other, you simply have to disable source control binding (for AnkhSVN) or disable the plugin (for VisualSVN).

In my experience, though, I've found that VisualSVN was a much better client than AnkhSVN. VisualSVN handles ignoring user files (*.suo) and adding projects to Subversion very efficiently. AnkhSVN on the other hand, caused me some difficulty.

Hope this helps!

mbmccormick