Error
TF30170: The plugin Microsoft.ProjectCreationWizard.TestManagement failed during task TestResolutionState from group TestManagement.
Explanation
Plugin error text: “System.MissingFieldException: Field not found:
'Microsoft.TeamFoundation.TestManagement.Common.WitCategoryRefName.SharedDataSet'.
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject.get_SharedParameterDataSetWorkItemTypeName()
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject.get_HasSupportForSharedParameterDataSets()
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject..ctor(TestManagementService
manager, String projectName) at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementService.b__0(String
name) at
Microsoft.TeamFoundation.TestManagement.Client.ObjectCache`2.Get(Key
key, Creator creator) at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementService.GetTeamProject(String
projectName) at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.ContextWrapper.get_Project()
at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.PcwPluginComponentCreator.SetPermissionsIfNeeded(ContextWrapper
wrapper) at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.PcwPluginComponentCreator.Parse(ContextWrapper
wrapper, XmlNode taskXml, Boolean fExecute)”
User Action
Contact your Team Foundation Server administrator.
I just saw this exact problem (TFS 2013 Update 4 and Visual Studio 2013 Update 4). I found the solution posted here on the Microsoft Connect site solved the problem. In short, uninstalling some assemblies that were mistakenly installed got everything working again.
1. Close all instances on Visual Studio and Microsoft Test Manager
2. Open Visual Studio command prompt in admin mode.
3. Perform the following steps:
ngen uninstall Microsoft.TeamFoundation.TestManagement.Client
ngen uninstall Microsoft.TeamFoundation.TestManagement.Common
I have seen this issue when the version of Visual Studio is not upgraded to Update 4 and an attempt is made to create a new team project. I would suggest that you first make sure that the version of visual studio (that you use to create the new team project) is on the same version as TFS (in this case Update 4).
I found a workaroud on msdn forum
There is a bug in the V1.0 version of the product that impacts Team
Project creation when the Team Foundation Administrators group has a
TFS project level group in its hierarchy. One way that this might
occur is if you try to open the system up by adding the Team
Foundation Valid Users group to the Team Foundation Administrators
group, though any TFS project level group will trigger the condition
(e.g., [project A]\Project Administrators). This issue only impacts
Team Project creation and it can be worked around by temporarily
removing the TFS project level group from the Team Foundation
Administrators group. There is a variation on this Team Project
creation bug that will appear if the sync process runs across a user
that does not have a valid security identifier. I am not quite sure
if your case of deleted domain users triggers this condition, but I
will follow up to find out. In the meantime, please take a look at
the membership of your Team Foundation Administrators group to see if
there are any TFS project level groups in the hierarchy.
I don't know if Microsoft had realeased a patch for this bug but for now I choosed to return to TFS 2012 which works like a charm
Related
When deploying plugins using the Visual Studio Microsoft Dynamics 365 Developer Toolkit, we have been plagued with duplicate steps being created.
If we find a duplicate step has been created, we delete the plugin from the server and then redeploy the plugin from Visual Studio using the right click, deploy method.
The RegisterFile.crmregister is under source control so the guids should be maintained whichever member of our small team deploys.
Why are the duplicate plugin steps being created and how can it be prevented in a team situation?
I am trying to add new projects to the Team Foundation Server and every way I have tried to add them has failed. We are running TFS 2012 Version: 11.0.50727.1 (RTM) and I am running Visual Studio 2015. I am a member of the Administrators Group.
I have tried at least 3 ways that MS support says how to do it on the website and none of them have worked:
I have tried to add it through Visual Studio
I have tried to add it through the Team Foundation Server Administration Console on the Server.
I have tried to add it through the TFS Web Management Portal.
When I try to add it through Visual Studio, I get an error when trying to check it in. It shows on the Source Control Explorer with a pending change of 'Add'. Here is a screenshot of the team explorer and output:
Since the message tells me to add it to the server, I opened the TFS Server Admin Console and When I go into the Team Projects Tab under Team Project Collections, it lists the existing projects, however, there is no way to add a new project. Here is a screenshot of the Admin Console:
There is only a help icon with a link on How to add a Team Project, although like with most MS help articles, it is useless. It provides information about how to do it on the web. So I tried it. I accessed the web portal for our TFS server and there isn't any option to add a project there either. When I go in to the "View the collection administration page" It tells me "Not all Collection level administration is exposed in the web experience. For all administration operations at the collection level please use the Administration Console on your Team Foundation Server.". Here is a screenshot of the online portal:
Can someone please help me with this issue? How can I add the projects to the Team Foundation Server?
I figured out how to Add the projects to the Team Foundation Server using Visual Studio 2015. It is very simple and can be done right from the File Menu in Visual Studio.
First open Visual Studio 2015. (I am not sure if it works the same in other versions.)
Go to File -> New -> Team Project...
The New Team Project Wizard will popup where you can then enter the project name and project description.
Then you can choose the template type and whether you will be using TFS Version Control or Git Distributed Version Control.
Once you click Finish, the Project will be added to TFS.
You can then add the files to the workspace folder on your dev machine.
Then you can check the files into TFS using the Team Explorer. *Note: First, you may need to add the files to the project by going to the Solution Control Explorer and right clicking on the newly created project and selecting Add Items to Folder. From there you can add the files then check them in using the Team Explorer.
Please clarify you want to create a code project/solution and add it to a TeamProject, or you want to create a TeamProject. TeamProject and code project/solution are different.
If you want to create a new TeamProject, according to Client compatibility, TFS 2012 supports VS 2015 RTM or latest update. Check your VS 2015 edition and re-try to create a TeamProject.
If you want to add a code project/solution to a TeamProject, you'll have to connect a TeamProject first and create a workspace, then perform a check-in: https://www.visualstudio.com/en-us/docs/tfvc/set-up-team-foundation-version-control-your-dev-machine
Last, try to clean the Cache folder on your dev computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\4.0\Cache.
If none of above works, try on another dev machine to see whether you can reproduce this issue.
I have recently migrated a number of apps created in Visual Studio versions 2005, 2008, and 2010 to VS2013. When I tried to check them into our TFS install, I was greeted with a message telling me that I needed to use a newer version (of TFS).
I contacted our server admin and got a share set up on a new version of tfs.
How the heck do I go about adding to the new TFS share? It is showing on the server (with the plus signs), but when I try to check-in the code, it complains at me telling me to first create a Team Project.
Do I need to create a blank Team project then copy all of my files in, or is there a shorter way?
Thanks in advance.
If you have an existing TFS server then you should upgrade it rate than copy stuff to a new server. It sounds like your existing server is TFS 2008 so you would need to upgrade to 2012 and then to 2013. No big deal, just a little more rigmarole.
If you are set on just pushing your code to a new server I would instead recommend that you create an account with Visual Studio Online (http://tfs.visualstudio.com) and use that.
If you are just going to shove it in the new TFS 2013 server that your infrastructure guy knocked together then you will need to create a Team Project first.
https://msdn.microsoft.com/en-us/library/ms181477.aspx
Can I have some basic project management in Visual Studion without TFS or is TFS what I need?
Basically I like to get a list with my projects, last edited dates, and if possible project tags (customer for example), and when selecting one VS should load it. From the right repository (Mercurial/Git/Svn). I can move my project to some repo host if they have this solution (Addon).
At the moment I handle the projecs manually with Windows standard folders + SVN/Hg in folder context menu, and thats a headache.
Thank you
As far as I know Visual Studio doesn't support that functionality natively.
TFS isn't my forte but I know it comes with MSDN subscriptions and the retail version is around $500 if that is the path you are interested in. If you do go the TFS route you have an option to use TFS Basic during install which is a greatly simplified install of TFS that can even use SQL Express.
You can check out pricing and download the trial from here if you want more info:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/team-foundation-server
We want to run our unit tests on our TFS server. We are running the database, TFS and the build agent on the same machine.
We have set it up and it appears to work up to the point that MStest tries to publish the results to the TFS server.
We get the following error:
The "TestToolsTask" task is using "MSTest.exe" from ......
Invalid switch "/publish".
Invalid switch "/publishbuild".
Invalid switch "/teamproject".
Invalid switch "/platform".
Invalid switch "/flavor".
For switch syntax, type "MSTest /help"
MSBUILD : warning MSB6006: "MSTest.exe" exited with code 1.
We think that the reason why we are getting this is that we have installed the professional version of Visual Studio on the build server.
Question is: Do we have to install a Team System Edition of Visual Studio on the build server or will it work if we just install the TFS client?
Thanks
Shiraz
We did this and I am pretty sure you need to install a version of Visual Studio Team Edition in order to publish a test to TFS :(
Found this link that says the same thing.
I am not 100% sure on this, but I'm fairly certain you need to install the Team System Edition of Visual Studio.
The client is just that, client software. Including items such as Work Item Tracking, Source Code Control, etc ... What you're looking for is the server side of the functionality and that comes with the team system edition.
To publish unit test results from the build, then you need to install a Team Edition of Visual Studio - either the Developer or Test edition will do. MSTest.exe is available in other versions of Visual Studio however when you go to publish test results it will throw an error. IMHO, the way that licensing works is that you can install the team edition on the build server provided the people checking in code (such as test code) have licenses - however you'll want to check with your Microsoft representative.
Yes, you need to install (at minimum) the extra tools that come with VSTT (Team Test) or VSTS (Suite) editions. The basic ability to write & execute unit tests inside VS were moved down from VSTT -> Professional in the 2008 product editions, but the specific scenario around publishing tests on the server was not.
As a general rule MS developer tools are licensed per-user, not per-machine. 2008 adds a few exceptions to the rule when it comes to non-IT staff use of work item tracking, but for the most part it still holds. Complete details: VSTS 2008 licensing white paper
Well, you can go a bit hacky and adding some registry data everything works ... Reflector is your friend ... just in case it helps ...