magius
magius

Reputation: 901

Problems using SVN with VS 2008

I've been reading about how SVN works with Visual Studio. I'm using VS 2008 and worried about possible problems of using SVN with VS 2008.

Can anyone share their experience with SVN + VS 2008?

Thanks heaps!

Note: I realized throwing GIT into the mix kinda diluted the real question I wanted to ask. So, I've restricted the question to just SVN + VS.

Upvotes: 3

Views: 501

Answers (8)

jussij
jussij

Reputation: 10560

The Agent SVN is MS-SCCI plug-in that works with Visual Studio and because it is MS-SCCI, it integrates directly with the source control menus found in Visual Studio itself.

Upvotes: 2

Rollin_s
Rollin_s

Reputation: 1983

You have several options for SVN + VS2008.

1) Use TortoiseSVN without integrating with VS2008. This is what I use most of the time and there's no issue. (If you don't mind leaving the IDE once in a while)

2) Use TortoiseSVN and integrate it with VS2008 yourself by mapping your custom toolbar buttons to TortoiseSVN automation commands. See this blog

3) Use VisualSVN (These guys fully integrate TortoiseSVN into VS2008 for you!)

4) Use AnknSVN (free and open source, but its not based on TortoiseSVN)

Upvotes: 1

JesperE
JesperE

Reputation: 64414

Good IDE-VC integration is most important when your IDE supports refactoring-operations which include renaming files. Using Eclipse JDT without Subversion-integration would be hopelessly inefficient since a renamed class would reappear after an "svn update" unless Eclipse informed Subversion that the file has been removed.

If you aren't doing any such "filesystem-altering" refactorings, VC-integration in your IDE is not terribly important, and you can do fine with for example TortoiseSVN.

Upvotes: 1

jwanagel
jwanagel

Reputation: 4069

TortoiseSVN is really good, but VisualSVN is fantastic if you're using VS 2008. Git is terrible for VS developers (or for running on Windows generally).

Upvotes: 1

cjs
cjs

Reputation: 27231

You're going to see much bigger differences due to the different paradigms of svn and git than you will through anything related to Visual Studio integration.

Explaining these differences is a bit of a job, and either one will make your life happier in various ways, so I wouldn't worry about which one you use. You can always change later, and you won't truly understand the differences until you've used both, anyway, if you decide to go that route.

Upvotes: 0

Gary.Ray
Gary.Ray

Reputation: 6501

I've used SVN both with and without IDE plugins in VS 2008 and have seen no issues.

Upvotes: 1

Marc Gravell
Marc Gravell

Reputation: 1062975

Personally I don't get too excited about IDE integration; I use TortoiseSVN in explorer, which IMO works just as well, without adding more weight to VS. AnkhSVN, Visual SVN and SlickEdit Versioning Toolbox are among the integrated tools.

But from what I understand (from dialogue only), Git != SVN...

Upvotes: 2

Gromer
Gromer

Reputation: 9931

You're going to need a plugin to interface Visual Studio 2008 with svn. Ankh seems to be pretty popular and I've heard of Visual SVN.

Upvotes: 2

Related Questions