I've been doing more research into using a Mercurial repository with TortoiseHG, and given the issues using svn from Codeplex that impact a significant number of people, I've decided to ask Codeplex to create a new Mercurial repository. It may take a day or so to get it all setup but there are a number of advantages to Mercurial. This blog post asks about the benefits of a distributed source code control vs centralized (like svn) and there are a lot of good comments on the post that do explain the benefits. If it doesn't work out well I can always ask them to change back, it would be kind of a pain all over again but I have a feeling in the long run using Mercurial with TortoiseAG will work out better.

I'll post again after the new repository is setup.

Best,

Joe

Hi All,

I've updated the document Getting the Code with TortoiseHG to clarify the update process, there are actually 2 steps, previously I had said all you need to do is TortoiseHG > Update, but that is not correct, there is one other step you have to do first to pull the change sets down from the server. Update only applies the change sets, so it won't do anything unless you first Pull the changes from the server.

I can say that using TortoiseHG/Mercurial so far has been a joy compared to TortoiseSVN/svn. The merging process is much smoother and much faster. It used to take me several hours to merge my changes from my sandbox into trunk whereas now it only takes a few minutes to merge changes from my development branch back into the default branch so I can get changes into your hands much faster now.

Best,

Joe