@Grovesy said:Though, I am a big fan of Tortoise, I have to hates in this world... one is integrated source control into Visual Studio.. for some reason it feels so clunky and 1/2 the time the plugin is so badly coded that it hands VS.net. The other is thick client source conrol IDE's where you have to go in and manullay checkout files and check them back-in... for me, the thick client seperate IDE is the lesser of the two evils.. I would rather use command line toosl....So when I found Tortoise and Subversion... I could just navigate within Explorer, find the director I wanted to check changed in.. right click.. .commit... comment... go... no conflicts. done.. (and it's all transactional on a changelist.. which is oddly enough if you have used things like VSS or any Serna product such as Dimmensions a luxury!) Ya, perforce integration with VS was so annoying I turned it off. It must be that the API for source control plugins is a bit gross, otherwise somebody would write one that works well. I notice that Perforce' visual studio plugin doesn't pick up the current clientspec correctly, causing all sorts of woe.p4 command line and p4win are perfectly analogous to svn command line and tortoise, when you're using 'out of the box' perforce. They're good and also don't assume too much. I'd say the main problem I have with perforce is as yours; that you have to be online to 'check out' a file. Perforce' documentation and interface encourage integration with other software, and programmers get complacent and call it from inappropriate places (even the UI). Imagine the sorrow when 100 artists spend an hour with an empty white rectangle where the art tool should be, waiting for a dead router to be reconfigured and put in place, so that perforce can set the 'checked out' flag on a file in the server. Now imagine the further woe when the router comes back and all 100 do it at once :-). Despite this, network outages are rare enough, and if you don't write yourself into such a dreadful corner, the situation isn't bad.