If you have tried to create a new Team Project from Visual Studio 2010 against a TFS 2012 server, you have undoubtedly encountered this error message.
After doing some research, it’s quite apparent that some changes were made to Team Foundation Server that make project creation incompatible with older TFS Clients. The error message actually doesn’t have anything to do with permissions, and during the beta for TFS 11.0 the error message was inaccurate and vague. I came across a statement by Buck Hodges, the current Director of Development for Team Foundation Server:
You must use the Visual Studio Team Explorer 2012 (included in all Visual Studio editions or may be separately downloaded) to create a team project on a TFS 2012 server. If you use VS 2010, you will get an error about not having permission. The error message is very misleading, because it’s not a problem with your permissions.
A bug was even reported, but closed by Microsoft, so it appears there are no plans to resolve this. Unfortunately sometimes this is the cost of adding features and releasing new versions, and you can still use Visual Studio 2010 SP1 against TFS 2012, just don’t expect to be able to create projects. Something to consider when thinking about migrating to TFS 2012.
Related Posts
ViewModel constructors and inheritance by extending kendo.data.ObservableObject
Exploring Active Record as a base for business entities in a business logic layer with Entity Framework- Using your own database schema and classes with ASP.NET Core Identity and Entity Framework Core
- Using DataTestMethod and DataRow to pass parameters to a unit test and prevent duplicating test methods
- Building SSDT SSRS projects (.rptproj) with a build server (TeamCity)
- Threads, locks, deadlocks, race conditions, and thread safety in multi-threaded code
Thank you for the posting. Agree with Vickie it is frustrating.
I’m running VS2010 and unable to create any new project team. I can do so after installing the Team Explorer 2012 (without the VS2012 installation as prerequisite). So it is a handy tool to achieve the goal I think.
Thank you so much for posting this! What a frustrating error messages when the security permissions had been checked and re-checked to no avail. This is the typical Microsoft half-baked scenario.
I’m glad this helped you. The TFS team is pretty small, less than 10 people if I am not mistaken. I agree though, there are some critical features I think are missing from TFS and this would be one of them.