![]() ![]() To me, it’s definetely the worst installation experience I’ve ever had with a Microsoft product. Installing TFS 2008 over SqlServer 2008 is quite complicated, you cannot install TFS on a PDC, etc. Installing TFS is quite a pain, while SVN installation is a matter of minutes. To stay fair, here are the two obvious drawbacks of TFS : ![]() I’m not saying it’s not possible to do the same using SVN and other third-party tools, but it’s definitely nice to have all things nicely integrated in one product. I’ve used it on a medium-sized project (12 coders, 3 testers, 3 business analysts) in the past, and we’ve been able to successfully centralize all the tasks in TFS (bug reports, project documentation, build process, etc.) TFS is more than just a source-control tool (think work items, project portal, etc.) While I think those reasons are more than enough to prefer TFS over SVN, I mus add that : csproj files, so you’ll need to manually edit them to open them again from VS.) Merging is a lot easier with TFS, even for complex merges (for example, SVN will add >’s to your. Almost all TFS tasks are accessible in a few clicks on the solution explorer tab. While Source-Control related features of both systems are probably quite equivalent, they are accessible directly from the IDE with TFS, while you have to rely on TortoiseSVN or other external tools if you use SVN. I’ve had my whole workspace corrupted several times using SVN (during one month), never using TFS (aprox 2 years) ![]() SVN integration into Visual Studio is incomplete to say the least (a lot of features aren’t available from the IDE), and a bit buggy (AnkhSVN certainly is), while TFS one is perfect (which makes sense…). Well, to me, the choice is obviously TFS : ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |