My team have particularly found SVN great for geographically distributed development efforts. We also like the fact that it sits outside of Visual Studio, meaning Visual Studio doesn't get to stuff things up with its crappy source control integration. (Of course, if you _need_ the source control integration for some unimaginable reason, there are tools out there that integrate SVN with Visual Studio.) I can't recommend SVN highly enough!!
shane day
Posts
-
That's it, I'm ditching CVS! -
Ideal Intranet Speed...Yup, my ADSL2+ is currently connected at 18Mb/s downlink with a 1MB/s uplink. And I thought Australia had poor broadband speeds compared to other industrialised nations! Incidentally, my ISP has just launched their ADSL2+M service, which allows you to sacrifice some downlink speed for greater uplink bandwidth. Might be useful if I need to host something temporarily.
-
No Vegemite for you!Yeah, you haven't suffered terror until you've experienced heart-burn from having Vegemite too thick on your toast. It could bring a whole nation to its knees. (BTW, Vegemite rocks! Just don't spread it too thickly!)
-
Source control (VS2005 integrated, comunity approved)We recently switched from SourceGear Vault, which is an excellent replacement for Visual SourceSafe (this program is a no-no!) and integrates well within VS2005. Our development team is distributed around Australia, and we were using SSL to access the Vault. However, source control integration in Visual Studio we found gets in the way - we find the paradigm in Subversion much more palatable. Also as it is Open Source if we add a new developer we don't need to worry about license costs. Tortoise works extremely well and its diff/merge tools are the best I've seen. We've been much more productive with Subversion. There are a few Visual Studio integration tools for it, but I've actually appreciated not having source control in Visual Studio.
-
Progging to Music!Progressive house gets me in the coding zone.