I am using Visual Studio Ultimate which come with TFS. However I am using Visual SVN as my source control.
I have installed VisualSVN server and the Visual Studio plug in.
What should I do to switch from TFS to Visual SVN.
When I go do Tools/Options/Source Control/Plug-in selection, I have the choice between "None" and TFS.
VisualSVN automatically "just works" when you open a SVN working copy - you don't need to mess with Visual Studio's SCC plugin settings. So you need to look at migrating your source code code into the SVN repository first. When you've done this, just check it out, open the solution and you're done. (You may want to remove all the "SccProjectName/SccProvider..." garbage from your project files beforehand)
To migrate your repository history from TFS to SVN, there's the TFS2SVN project (I've not used it though).
If you're not stuck on VisualSVN, try AnkhSVN. We use that here, and had no issues in getting it to work with VisualStudio 2010.
AnkhSVN is an open source plugin, so there's no need to pay for a license.
If VisualSVN is like AnkhSVN, you need to in tall VisualStudio first, then AnkhSVN. Then go into VisualStudio and select SVN in the Source Control Plug-in selection.
Related
I installed TortoiseSVN and AnkhSVN and restarted my PC. However, I can't find subversion link in File -> Open and AnkhSvn does not show up in source control in Tools -> Options -> Source control.
I have tried uninstalling and reinstalling TortoiseSVN and AnkhSVN as well as Visual Studio 2012 with no success.
Can someone please help me with the integration of the SVN and Visual Studio 2012 Professional?
Since reinstall didn't help, i.e. you still don't see AnkhSVN as a source-control provider in Visual Studio, then it might indicate a bug or some problem with Visual Studio itself. I guess that you might get more help on this issue if you contact AnkhSVN user discussions mailing list.
BTW, AnkhSVN does not rely or require TortoiseSVN client. Since you mentioned TortoiseSVN, then I suggest trying VisualSVN plug-in. If you are familiar with TortoiseSVN and like it then I'm pretty sure that you'll find VisualSVN very friendly and easy to use with practically no learning curve.
I had the same issue; the root cause is that registry is not correctly written during installation. Visual Studio Source Control Plug-In Selection drop-down list links to the registry directly.
My regedit had been disabled by system admin, so that the installing was failed (but you would not get any error message).
Re-installing AnkhSVN after enabling read/write permission of registry and the issue gets solved.
I am using ankkhsvn (selected as an option in tools) in visual studio 2010 and when I restart my machine the project reverts back to Team foundation as the selected source control.
Any ideas?
Right click solution, add to subversion. confirm that you want to manage the .sln with subversion.
This adds a few lines to your .sln that enable AnkhSVN if it is installed (or are ignored if AnkhSVN isn't installed).
I was using Visual Studio 2010 previously, with visual SVN as the source control. Now that I've upgraded to Visual Studio 2012, I'm facing problem of adding SVN as the source control (to VS 2012). By default only Team Foundation is there. Any help with how to add SVN as the source control to Visual Studio 2012 would be really appreciated.
VisualSVN 3.0 supports Visual Studio 2012. You can get it at the download page.
Except VS2012 support and a couple of usability and UI improvements VisualSVN 3.0 introduces the new Community License that allows to use VisualSVN for free on non-domain machines (moreover it permits commercial use!). See the VisualSVN 3.0 Release Notes.
In VS2012 just go to Tools/Options/Source control and in dropdown "Current source control plug-in" select the needed one (if you already have it installed)
Run the Visual SVN installer again and select 'Modify'
Tick the box that say 'Integration Visual Studio 2012'
and then continue with the installation. Restart VS 2012 and you will see VISUAL SVN on the TOP menu
We use AnkhSVN for VS2012 and lower versions.
Most likely you're using old version of VisualSVN that doesn't support VS2012. Try to install latest VisualSVN 3.0 for Visual Studio 2012 support.
Currently I am using VisualSVN-5.1.4, but I have done this with previous versions.
Re-run the installer.
Select "Modify", then Next to move to the "Custom Setup" pane.
A checkbox list of the installed Visual Studio (VS) versions will appear.
Check to VS('s) that apply.
Open the targeted VS.
Open the "Tools>Options" dialog and select Source Control
Select "VisualSVN" from the "Current source control plug-in" combo box.
I first took the "Repair" option but that did not put VisualSVN in the Source Control options list. It didn't hurt but it didn't help, either.
Yo need to run the installer of subversion again and repair the installation.
The installer will register the application in the VS2012 version too.
We had the same problem with it.
What you really need to do is go to Tools -> Options
In the dialog scroll down to Source Control -> plug-in-selections.
There is a drop down that has a list of source controls and you select your SVN controller there (Ankh, Visual, whatever one you want).
This is the same for 2012, 2013 and 2015
Re-run the installer , and during the setup, choose the versions of Visual Studio you want to be available.
The Eclipse IDE has a nice feature that automatically logs file revisions and you can view them anytime by right-clicking on a file and clicking on Compare With -> Local History....
Is there an equivalent to this in Visual Studio 2010?
Some more updated options:
Every save is stored in a git repository. You can use existing git tools to look at the history:
autogit
This extension provides a custom local history viewer:
Local History for Visual Studio
Local History for Visual Studio is similar to Eclipse or IntelliJ's local history feature. It works with Visual Studio 2012 and 2013.
There is not natively in Visual Studio but what about Visual Local History. It has the option to 'Compare with last version'. It should work well for VS 2005, 2008 and with some extra configuration for 2010.
There is not an equivalent feature for local history.
However, if you're using TFS, there is support in the IDE for getting history of files (though this is commited/checked history).
Many other version control systems also have plugins for Visual studio which provide this type of functionality. For example, VisualHG provides an "HG History" command which shows the version history in the Mercurial repository.
For Visual Studio 2015, 2017, 2019 VSHistory extension: maintains the history of files in your Visual Studio projects every time they are saved. Any saved version can be viewed or a diff with the current version can be displayed
I'm trying to set up a new Windows computer with Visual Studio 2008 to work on a Sourceforge project I maintain. I'd like to use a distributed version control system (tried SVN, didn't like it).
I've used git and mercurial before on UNIX, but I'm having no luck finding a quality plugin that integrates in Visual Studio 2008 and allows me to work on my Sourceforge code.
Can anyone provide some suggestions on how to progress?
Should I just use Eclipse instead?
I've been using Mercurial with VS 2008 for a while now and have found that a combination of TortoiseHg and an open command prompt solves most issues. Prior to Mercurial, we used Microsoft Visual Source Safe (VSS) with Visual Studio integration. Even with the plugin, you still had to go into VSS to create projects and do some project management stuff, so you still had to know how to use the source control tools outside of the IDE. After the change, I even toyed with the idea of writing a Mercurial plugin for VS 2008 myself. Before I could do that, I had to familiarize myself with Mercurial. While doing that, I found that it took a little while to get used to doing source control outside of the IDE, but I now prefer the command line and TortoiseHg tools to the VSS IDE plugin.
However, there do seem to be a couple plugins for Visual Studio available for Mercurial:
VisualHG
hgscc
I haven't tested them, so I can't give you an opinion on their usefulness.
Having never looked at the Eclipse plugin for Mercurial, I can't say if it is better than the command line method I use.