Skip to main content

Team Foundation Server 2010 Licensing

UPDATE: Since putting this article together MS have released their VS2010 and MSDN Licensing White Paper, which whilst it confirms all of the following should be used in preference to this information.

Original Article:

Firstly, a bit of a disclaimer - the following are just my observations / opinions only and should not be used to plan any purchase or decision.  I also have no association with Microsoft or any reseller.

As part of a new role I've recently been looking into the costs associated with rolling out TFS 2010 and whilst Microsoft seem to be making their product structure / licensing easier if the confusion surrounding TFS is anything to go by then they've still got a little more to do.

There are two main ways to obtain TFS:

  1. As part of VS2010 + MSDN, or
  2. As a stand alone product.

As far as I can ascertain both include exactly the same version of TFS. Along the VS2010 MSDN subscription a developer receives 1 Client Access License (CAL) for use with TFS.  This allows that developer to connect to any instance of TFS. The stand-alone TFS product does not come with any CALs, these must be purchased separately. However it does come with 5 EULA exception licenses (see following blog article). This allows up to 5 users to connect to that instance of TFS without needing a CAL. Note: you can not coalesce / merge these EULA licensed exceptions in that if you purchased two instances of TFS you would have 2x5 EULA exception licenses - if you had 4 users on one instance and wanted to add a 6th user to the other instance you would need to purchase a full TFS CAL for that 6th user, you could not transfer the unused license from the 1st instance to the other server. Also worth noting that in this scenario the 6th user that has the CAL would be able to use the 1st instance without using up that 5th EULA exception license.

Therefore if only developers are going to be accessing / using TFS and they all have MSDN subscriptions you do not need to purchase the standalone product.  However, if you wish for product managers and testers to access / use TFS, then you should probably purchase the stand alone product too, then up to another 5 people can connect to that instance of TFS along with the developers.


Post a Comment

Popular posts from this blog

Problem installing AWS CLI

It never feels like a good start when you're trying to start out with something and the install fails with an obscure error! I was just trying to install the Amazon CLI following the instructions at and ran into the following error when running 'pip install awscli': Collecting awscli Could not find a version that satisfies the requirement awscli (from versions: ) No matching distribution found for awscli I appeared to have a correct version of Python installed (v2.7) and checking "PIP -v" indicated that 9.0.1 was installed. That all seemed to tick the required boxes but digging around a little more I did see that some people had had issues with various versions of PIP so I found / ran the following to upgrade to the latest vesion: curl -o python This installed v9.0.3 of PIP which burst into life when I re-ran 'pip install awscli' and everything seems to be ok. Like…

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…