This blog post is comparing the current feature set of Microsoft’s hosted TFS solution – Visual Studio Online (VSO) and the on-premises Team Foundation Server product.
Feature Comparison (as of February 2014)
|
TFS |
VSO |
|
| Work Items, Version Control, & Build |
Yes |
Yes |
| Agile Product/Project Management |
Yes |
Yes |
| Test Case Management |
Yes |
Yes |
| Heterogeneous Development (Eclipse, Git) |
Yes |
Yes |
| Ease of Installation and Setup |
+/- |
++ |
| Collaborate with anyone, from anywhere |
+/- |
++ |
| Data stays inside your network |
Yes |
No |
| Process Template & Work Item Customization |
Yes |
No |
| SharePoint Integration |
Yes |
No |
| Data Warehouse & Reporting |
Yes |
No |
| CodeLens Support |
Yes |
No |
| Cloud Load Testing |
No |
Yes |
| Application Insights |
No |
Yes |
| Always running the latest version of TFS |
No |
Yes |
Remember: Visual Studio Online is currently a so-called “commercial preview”.
Some other limitations of VSO (as of February 2014)
- No Data Export (there are plans to make it available for a short time period)
- No Data Import (if you want to move from on-premises TFS to VSO)
- No Integration with Active Directory (users sign in using Microsoft Accounts)
- No choice of geographic location (data stored in data center in Chicago)
–Neno
Maybe not a “feature” per se, but I would also include “Do not want to maintain TFS servers” – TFS: No; VSO: Yes (or something to that effect).
Nice post!
Implementing Continuous Delivery with VSO - Please Release Me // Mar 8, 2015 at 14:51
[…] approximately every three weeks so it contains new application features well ahead of TFS. A post here has a nice comparison. What you may find interesting is that as per Brian Harry’s blog post […]
Migracja projektów TFS on-premise do VSTS – Chmuroman // Jun 22, 2016 at 10:56
[…] w centrach danych na całym świecie. Główne różnice pomiędzy TFS i VSTS znajdują się w tym wpisie na blogu jednego z MVP. Najważniejsze różnice to jednak sposób hostowania serwera (on-premise […]