Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
We started building SourceSafe in January 1992 in the vacated dining room of the house belonging to one of my partners. Within a couple of short years SourceSafe went from concept to major success and was acquired by Microsoft in 1994, soon after which it became the most widely used version control system in the world. The thing that was truly novel about SourceSafe in the early 1990s was that it was really easy to learn and use. People tried it and just liked it. It wasn’t the most powerful system around but it had what people needed and was a refreshing break from complicated command line oriented interfaces.
However SourceSafe was designed and built in the early 90’s and a lot has changed since then. Technologies are different – the internet really didn’t exist in a meaningful way (web browsers were in early experimentation), databases were still complicated products primarily used for enterprise mission critical data, etc; and development is a lot different – projects were much smaller and less sophisticated then. The emergence of Visual Basic in the early 90’s really changed the landscape of development and brought a lot of people into the field who would have never previously considered it and made custom software a much bigger part of people’s lives.
Other trends have developed and gained a great deal of momentum. Frustration with traditional ways of executing software projects, the Agile set of development methodologies have become VERY popular, bringing with them a new set of practices - unit testing, continuous integration, TDD, and more.
Right around the beginning of 2003 – almost 11 years after beginning the SourceSafe journey, I and a few other people embarked to create Team Foundation Server. The goal was to create a development team collaboration product that would meet the needs of virtually any development team for the next couple of decades. It is based on modern technologies – SQL Server, ASP.NET, Web Services, .NET, etc. And it takes a comprehensive view of the software development lifecycle, with the intent of ultimately addressing all phases and all participants.
To make sure we could handle the broadest range, we started by targeting enterprise customers and development teams with more involved development processes. The pinnacle of that has been the Microsoft Developer Division experience that I’ve talked so much about where we have over 3,500 regular users and terrabytes upon terrabytes of data. However, it has been our intention from the beginning to build a toolset that is attractive to teams of all sizes and all levels of process.
For smaller teams, the most common complaints about TFS 2005 were that it was expensive, difficult to install, difficult to manage and required onerous pre-reqs. We made good progress on the setup experience in TFS 2008, although most of that was oriented towards enterprise customers who needed more installation flexibility.
Fast forward now to TFS 2010…
TFS 2010 represents a huge step forward in making TFS more approachable by smaller teams. With software development technology continuing to advance and SourceSafe slowly looking older, TFS 2010 is a great opportunity for SourceSafe users to look at updating their toolset.
So what’s different about TFS 2010?
There are 3 main areas that we’ve focused on in 2010 to make TFS attractive to smaller teams:
And that’s it – TFS is installed and ready to use. There’s a similarly (but not quite as) easy wizard for configuring a build server on the same machine…
All of this gives you a development system with Version Control, Bug tracking and build automation (making continuous integration a snap!). What it lacks from Standard TFS is Sharepoint and Reporting capabilities. The great thing though is that TFS "Basic” IS TFS so as your needs grow you can reconfigure it to add more capabilities.
It’s a really exciting development and I hope you really like it. I encourage you to get TFS 2010 Beta 2 when it is available later this fall and give it a try.
As always, feedback is welcome!
Brian
Right around the beginning of 1993 – almost 11 years after beginning the SourceSafe journey
This should say 2003??
Can't wait for using TFS 2010! As you mentioned in your post, the pricing of the previous versions (2005 & 2008) was pretty high. We had a difficult time convincing our customers to use TFS, pricing was the major bottleneck! Will Microsoft also change their Visual Studio prices? Thank you
Thanks to all of you who pointed out that I screwed up the for TFS. Despite proof reading it, I managed to miss that :(
Antonacci, I don't think we'll be changing SourceSafe pricing. It's already pretty widely available and affordable.
No dependency on SP & Reporting, simple install, on domain controller,on 32 & 64 bit and that too on client OS's that is indeed a quantum leap. :):) Looking forward to getting it on my laptop. Congrats to the team on awesome release. :)
Some great changes here - I will start using this for personal projects at home. Hope it will install on a windows home server.
SOunds Good so far...
now the question is will i be able to get my boss to buy the Team SKU's of Visual STudio so that I can use this?
IMHO many of the tools in VS Team* should just be part of VS Pro or the prices for all of the SKU's need to go down a bit at each level.
Wow ... I have been banging my head around installing TFS on our dev server, with no luck.
Just can't wait for this to come out ... :)
Installation of TFS 2008 took couple of months from our IT. Simplifying installation is absolutely correct way to go. Keep on improving this great product.
I gave up installing TFS 2008 on SQL server 2008 and/or SQL server 2005. It was very difficult and did not work. Stupid SharePoint and reporting services were causing all sorts of issues. I will stick with SourceSafe for now. I use subversion which is very good. Have you guys address offline development issue. The biggest draw back from VSS and TFS is you have to constantly connect to source control. I hope M$FT fixes these issues in TFS 2010. Also, it makes very hard for some orgs to use additional license of SQL server. You should be able to use SQL Express version but it has size limit.
I still hope that you will offer a TFS Live or TFS Online, i.e. a cloud hosted option for the full TFS fun. After all, you need to do something with all your fancy data centers in any case, plus if there were simple/cheap/small packages available, this certainly would be an option with very little barriers for small shops.
Denny, FWIW, you don't have to have a Team System role SKU to use TFS. You can purchase a TFS CAL (for <= $500) and use TFS with Pro or other development environments.
Ross,
I have not tried it myself but I have a report from one of our MVPs that he installed it on Home Server and was working well.
developer,
No, unfortunately, we didn't make offline much better in this release. We added some support in 2008 to enable it and improved it in SP1. I'm thinking that will be an investment for our next release but we'll see.
Yes, SQLExpress has a 2GB limit per database. That will be an issue for all but small shops. However, once we announce pricing and licensing, I think you'll see that moving to SQL Standard won't be a big issue from a cost perspective.
David,
Yes, we agree hosting is a very viable approach for many customers. For now we have a number of options for people. Microsoft offer CodePlex for free for public development projects and we have several partners offering paid hosting.
There are quite a few out there. I'm fairly familiar with SaaSMadeEasy and TeamDevCentral. Both have low cost getting started kinds of options.