I have been using Mercurial with VS 2008 for a while and found that the combination of TortoiseHg and the open hint command solves most of the problems. Before Mercurial, we used Microsoft Visual Source Safe (VSS) with Visual Studio integration. Even with the plugin, you still had to go into VSS to create projects and create some project controls, so you still need to know how to use the source control tools outside the IDE. After the change, I even played around with the idea of โโwriting a Mercurial plugin for VS 2008. Before I could do this, I had to familiarize myself with Mercurial. While doing this, I found that it took a little time to get used to managing the source code outside the IDE, but now I prefer to use the command line and TortoiseHg tools for the VSS IDE plugin.
However, it seems that several plugins for Visual Studio are available for Visual Studio:
I have not tested them, so I can not give you an assessment of their usefulness.
Having never looked at the Eclipse plugin for Mercurial, I cannot say if this is better from the command line method used.
source share