1.) Is impossible to answer objectively. There are no git visual studio plugins so using either from Visual Studio is completely dependent on which one you like better. For me, it is bazaar because its rename support is truly rename (not a remove than add), and it supports versioning directories (which I have found quite handy). But if I was picking between git and mercurial, I'd use mercurial but only because I have more experience with Mercurial than git and I find it works better with Windows (git works fine with Windows just not as cleanly in my opinion).
2.) Nope. But I tried VisualHg (http://visualhg.codeplex.com/). And it pretty nice. I don't know if all the features are solid, but the "hidden" ones that I used (rename files, rename directories, etc.) worked without me having to drop to the command line to fix things up before commit. 3.) I don't know about git, but with Mercurial securing access to the repository was hit or miss. We served up the central repository behind an IIS box. We put ACLs on the repo and sometimes they worked, sometimes they didn't. Never really debugged it to a root cause... On Fri, Dec 10, 2010 at 8:10 AM, Shawn Neal <[email protected]> wrote: > TFS and it's nanny checkout system has annoyed me for the last time, so I > was hoping to solicit some feedback from other's who might have moved away > from centralized revision control system to a DRCS like Git or Mercurial. > Our development team has experience with both Git and Hg, but for non .NET > development. I worry about how well these two play with Visual Studio; I > suspect without some sort of VS integration it'll be harder to use than TFS > especially for renames. > > 1. For .NET development with VS 2010, which works better, Git or Hg? > Why? > 2. Do you use any source control plugins to VS? Which one? > 3. When moving from a centralized version control system to a > distributed one, what are some things to watch out for? > > Thanks in advance, > -Shawn > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<altnetseattle%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
