I am looking at upgrading our development from a very old version of Source Control to Team Foundation Server 2010, although I have some questions around what I actually require to get TFS up and running. The current team consists of 18 application/web developers and 4 web designers, all use Visual Studio 2010 Professional as the primary development environment. Visual Studio is licensed as either Professional with MSDN or full MSDN subscription. So based upon those details I believe that I am looking at the following:
- Hardware: A suitable server will be provided and IT will implement into our AD network
- One Team Foundation Server 2010 license and use the SQL license provided with TFS
- One External Connector License
- Individual client access licenses (CAL) for the develops where it is not included as part of the Visual Studio/MSDN license
Is this correct or is there something I’ve missed?
Thanks in advance,
I know but when MS products are your choice and the business is already using SharePoint, exchange etc it makes sense to use TFS. Plus there is the added bonus of the deployment options.
That said, I would be interested in what the other options are
Probably sounds good, though I’d save the $10k or so and use lots of the better, cheaper options that are about.
Well, I’ve bought more than my fair share of MS products and services. But source control is something they just don’t do well, or nearly as well as the FOSS guys who have been solving this problem alot better alot longer.
I would use something like:
Source Control: hosted Mercurial on bitbucket.org. Reason for hg over git is hg tooling is alot better than git tooling on windows, and hg integration with visual studio is also a bit more “there”.
Issue Tracking: redmine all the way. Integrates with just about anything under the sun SCM-wise. Integrates with AD authentication-wise while also being nice and pretty and usable.
Continuious Integration / Deployment : TeamCity. Really a very well designed, well thought out product. Can build just about anything, so when your iOS app needs a build server you don’t need a whole new system to handle it. Also has very slick VS integration.
I don’t think TFS deployment would do anything I can’t do with a number of other things and it still rides on one building an app so it can be automatically deployed so it is kind of moot.