Check out Mercurial version control with my CodePlex repository

Mercurial SCM (Hg) is a Distributed Version Control System (DVSC).  More importantly, your code doesn’t know or care how it is being versioned.  In other words, None of your VS solution or project files will be modified with a pointer to source control, and no *.scc files will be added in your code.

Interesting enough, Martin Fowler currently recommends Mercurial above the others at this point in time.

To get started, you will want to install the Mercurial Visual Studio 2008 SCC provider (for commits) as well as TortoiseHg, which is the tool you will use the most.

Check out my repository at http://palermo.codeplex.com with the getting started guide.  If you already know Hg, the Hq repo can be cloned at https://hg01.codeplex.com/palermo.

For those who are new to Tortoise, Here is how I would go about getting the source:

image

I do have TortoiseSVN, TortoiseGit, and TortoiseHg installed.  The experience is very similar among the tree, and they do not conflict with each other.

Comments

Erik Porter said on 2.19.2010 at 2:34 PM

We use it for Orchard and overall love it!

Kornelije Sajler said on 2.20.2010 at 3:12 AM

I think that the best, and fastest way of dealing with Mercurial (and Git) is through Command Prompt or like me in PowerShell. All you have to do is use this commands:

hg pull -u (pull and update) <br />

hg heads (and/or) hg merge (if there are conflicts, to see/to solve) <br/>

hg commit -Am "message" (include all files and message) <br />

hg push <br />

Much faster than any tool, but I use TortosieHg sometimes only for commits when I have to write long messages, and is not good experience in Command Prompt.<br />

I have made a Mercurial status in PowerShell prompt and <a href="http://bitbucket.org/xajler/powershell-prompt-for-mercurial/src/" target="_blank">source code is on BitBucket</a> and it is inside <a href="http://sourceforge.net/projects/console/" target0"_blank">Console2</a>, much better look'n'feel than Command Prompt. <br />

This is a <a href="http://www.markembling.info/blog/view/slug/my-ideal-powershell-prompt-with-git-integration" target="_blank">clone of Mark Embling for Git</a>), funny Jeremy Skinner also made same adoption few days ago.

Brian Sullivan said on 2.20.2010 at 5:49 PM

I don't think Mercurial has gotten enough good press in the .NET community. It runs great on Windows, had most of the features people like about Git, and is a bit easier to learn. Now that Codeplex is supporting it, hopefully more people will take a look at it. Thanks for posting this!

qj said on 2.20.2010 at 6:19 PM

"Mercurial SCM (Hg) is a Distributed Version Control System (DVSC).", DVSC should be DVCS.

Teme said on 3.01.2010 at 12:21 PM

Thanks for sharing Jeff. After reading your article, I set up Mercurial on my local on IIS with the CGI script and started playing with it. It is so fast and very sleek. Also features like the graph on TortoiseHg are so cool. Now in the process of setting mercurial repository on our integration build server and start using it for our new project.

Teme

Brian said on 3.20.2010 at 12:42 PM

Is there a reason you use Mercurial Visual Studio 2008 SCC provider instead of VisualHg? I haven't had a chance to try either and would be interested to know why you picked one over the other.

http://visualhg.codeplex.com