AnkhSVN all the way. Ankh is (now) a full SCC implementation. I have tried Visual SVN but found it has the same problems that Ankh V1 had. The problem is that VisualSVN needs to know intamate details about different project types, and it has to be coded to explicitly support them. This meant that when you use a unsupported project type you basically need to email them and wait for another release untill you can use VSVN on it. While if you use AnkhSVN 'it just works' and its GUI is well suited to Visual Studio - while VSVN simply puts up a modal box and shells to TSVN which does the real work. http://ankhsvn.open.collab.net/[^]

wow, personally a data binding model that actually works was enough incentive to use it for new projects.

> I'm actually an MD (Managing Director - not Doctor), but they don't have MD in the drop down. then fire his stupid ass seriously