 |
bluematrix
Registered: Jan 2012
Posts: 140 |
08-05-12 12:30 AM
what is the best system to be used with microsoft technology - visual studio?
1. Subversion/SVN
2. Git
3. Mercurial
4. Bazaar
edit: and what about Team Foundation Server ??
I appreciate serious input from your experience.
thanks
|
| |
|
Edit/Delete • Quote • Complain |
NetTecture
Registered: Mar 2009
Posts: 1018 |
08-05-12 07:35 AM
TFS, simply like that.
Your question has one big problem - you look at version control ONLY.
TFS gives you so much more fully integrated is not even funny - unit testing, work item tracking, integration with Sharepoint for documentation etc. and with the new 2012 version, out like any week now, even code reviews.
|
| |
|
Edit/Delete • Quote • Complain |
bluematrix
Registered: Jan 2012
Posts: 140 |
08-05-12 01:07 PM
Quote from NetTecture:
TFS, simply like that.
Your question has one big problem - you look at version control ONLY.
TFS gives you so much more fully integrated is not even funny - unit testing, work item tracking, integration with Sharepoint for documentation etc. and with the new 2012 version, out like any week now, even code reviews.
Have you used TFS extensively? how does its version control support compare to others (have you tried others?)
thanks
|
| |
|
Edit/Delete • Quote • Complain |
NetTecture
Registered: Mar 2009
Posts: 1018 |
08-05-12 01:34 PM
I do IT for a living for 20 years. Yes, I have used it extensively, as well as others. Right now with a customer I struggle using AcuRev and it's CRAPPY integration.
TFS is a Source control system that is centralized (good in my opinion - I want a central repository) and it does what it does well. Jsut it is not fair to use it as version control system. It does more - and the more make it dominating good. You do not have to use 4 or 5 different software packages, ONLY TFS. That is the main advantage.
Otherwise it has a good integration into Visual Studio. This is important if you compare it to the CRAP some others deliver in this place (AccuRev, for example) ;)
|
| |
|
Edit/Delete • Quote • Complain |
amazingIndustry
Registered: Aug 2009
Posts: 570 |
08-05-12 02:37 PM
TFS is great if you use VS, only. I love subversion/SVN the most because you can pretty much version control anything, even run backups of folders completely unrelated to code in .Net. I am not claiming TFS cannot do that (I doubt it at this point) but it will surely be more complicated than simply right-clicking any folder, adding and committing it. Microsoft generally makes things a lot more complicated, maybe to make the people who earned their MVP designation worth more than the paper its printed on.
I respect your experience, but TFS pretty much comes out in the bottom third in comparison with all other version control systems worth their salt. Check out posts at Stackoverflow, a site I really like and often peruse. Its a forum of/for/by professional programmers and IT related people.
Quote from NetTecture:
I do IT for a living for 20 years. Yes, I have used it extensively, as well as others. Right now with a customer I struggle using AcuRev and it's CRAPPY integration.
TFS is a Source control system that is centralized (good in my opinion - I want a central repository) and it does what it does well. Jsut it is not fair to use it as version control system. It does more - and the more make it dominating good. You do not have to use 4 or 5 different software packages, ONLY TFS. That is the main advantage.
Otherwise it has a good integration into Visual Studio. This is important if you compare it to the CRAP some others deliver in this place (AccuRev, for example) ;)
|
| |
|
Edit/Delete • Quote • Complain |
TheGoonior
Registered: Oct 2009
Posts: 836 |
08-05-12 03:13 PM
Quote from bluematrix:
what is the best system to be used with microsoft technology - visual studio?
1. Subversion/SVN
2. Git
3. Mercurial
4. Bazaar
edit: and what about Team Foundation Server ??
I appreciate serious input from your experience.
thanks
For a solo developer who is strictly looking for revision control, I think SVN is the best bank for the buck (given that it's open source). If you are dealing with a team of developers, the tight integration between your repository and your IDE, code reviews, and documentation are obviously strong selling points, but if you're just coding with VS out of your house, it's probably overkill.
|
| |
|
Edit/Delete • Quote • Complain |
| Receive
an email whenever a new post is added to this thread by subscribing
to it. |
|
|
|
|
