Visual Studio has built in hooks for adding in source control support. It's not really MS's fault that few take advantage of this. Whenever you create a solution one option is "add to source control", it's up to your current source control extension to take and run with it if you do check that box. In Tools > Options > Source Control, you can choose your source control plugin.
With that said, I never use source control within Visual Studio. I always have good ol' bash running git off to the side. I much prefer my IDE not know nor try to do too much, it often ends up in disaster.
Re:Visual Studio Add-Ins (Poll Result)
by kylechafin on Tuesday September 21, 2010 @11:56AM
(#1713048)
I've been using the VisualSVN plugin for the past few years and have found it to be really pleasant. It's $50, but it's been well worth it for me. http://visualsvn.com/
Alternatively, it sounds like AnhkSVN has been making some great strides lately, but a bad experience with it several years back has kept me away from it. They're free, so they might be worth checking out as well. http://ankhsvn.open.collab.net/
visualSVN is good and AnkhSVN is a decent free one. I've never placed a massive priority on source control integration to the IDE though, TortoiseSVN does fine for me.
What workflow do you use that requires it to be integrated into the IDE, or is it just a convenience thing?
Re:Visual Studio Add-Ins (Poll Result)
by henrikschroder on Tuesday September 21, 2010 @01:31PM
(#1713381)
The problem is that version control system integration in VS itself is usually worse than the same integration in the regular filesystem explorer.
If they only could get something that is on par with what Eclipse has I'd be very happy.
ReSharper adds a lot of features to VS that is standard in Eclipse and IntelliJ in the Java world, hence many people love ReSharper, esp transplants from the Java world.