SVN & TFS

Stefan_Lang

It used to be difficult to keep track of which versions you already had merged to a branch and which not, but since about 2 years SVN keeps track of that information for you: i. e. once you wish to merge back to head you can just merge the entire history since you branched and SVN will prevent any duplicate merges! If there are any other issues regarding branching (that other VCSs don't share) I am not aware of them.

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

Lost User

NO, I think TFS has a load more features, but you need to look at what you want or need - it's not worth spending money and additional time to learn to use features you don't need

MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

Br Bill

TFS is only for Build/Deployment engineers who can live with easy and simple canned functionality. My experience using it for build/deployment was miserable because we didn't fit the cookie-cutter methodology MS provided. I absolutely hate TFS.

DarkChuky CR

It just how you use it.... Both can be used just like a a sharepoint, just to store your files and have a single changeset-checkin id ot track changes... If you only care about storage and share SNV could be the best option, cause you don't need to install Visual Studio to access it.... but then the integraton with your Development IDE can be a pain. If you want to have more tracking, tickets and better contront on version and branches it's better to use TFS, it integrates all in one single IDE, ok you can add third party solution to your SVN and get the same but then you need to maintain 2 products.... So, both are good, at the end it's it just how you use and what can you pay for... (SVN with Trac is beautiful)