I will start by saying that I am not a developer, I use Visual Studio only for TFS as a means of contributing to Work Items in our project (I am a product owner).
On TFS web, there are some fields we have that give us a multiple-choice made up of a number of checkboxes. In the Team Explorer / Work Item view in TFS, these fields do not work and give me the following error:
Could not find a part of the path 'C:\ProgramData\Microsoft\Team
Foundation\Work Item Tracking\Custom
Controls\16.0\GLMultiValueControl.wicc'.
I assume what is happening is that this file defines the allowed values for this field, however the file isn't there. In addition, the following directory doesn't exist either:
C:\ProgramData\Microsoft\Team Foundation
Is there some command I need to run to synchronise my local copy of TFS with the server? I find it surprising that the Team Foundation folder doesn't exist, maybe I've missed something with the installation?
Related
Someone in my team has decided to delete old (unused) projects from our TFS Online server and now I see a bunch of GUID text in the Source Control Explorer in Visual Studio 2015.
On the right pane you can see that the projects do not exists on the TFS Online Server. Also, I logged in to our Visual Studio Online to make sure that its not there and its not.
I tried deleting the mapping and disconnecting from the server but when I connected back the GUID projects still there.
Also, I tried deleting the cache folder from "C:\Users\user_name\AppData\Local\Microsoft\Team Foundation\6.0" nothing helps.
The Guid in the middle (in the screenshot) seems to be mapped to a project that does not exists in my local anymore and I cannot remove the mapping.
Does anyone know how to delete these projects from my source control explorer?
by the way other developers see these GUID text too. Every developer sees it.
This issue is already reported here
Currently Azure DevOps Team is working on this issue for the fix.As of now there is no workaround for this. So, we have to wait for it.
I am attempting to edit our work item template for bugs in Team Services (Visual Studio Online).
I can successfully export a wit in xml, but when I try to import a wit I get the following error: tf237090 - does not exist or access is denied.
Things I have tried:
Check my permissions. I am running Visual Studio 2015 as administrator. In the DefaultCollection control panel in Visual Studio Team Services I am a member of the Project Collection Administrators group.
Export a wit, then immediately try to import the wit back to the server with no changes. Still get the error. This is using the Team Power Tools Process Editor in Visual Studio 2015.
Use the command line witadmin tool for Visual Studio 2015 (also ran the command prompt as administrator). I get the same error even if I export a wit, then try to import the same exact wit.
No file locks or open files. I have created a temporary directory to export the wit to and repeated all of the above steps without editing or opening the wit.xml.
Check the forums for the error code, I haven't been able to find any useful information except perhaps 3 year old posts about this not being a feature yet the Visual Studio Team Services help pages indicate it is supported. Similar questions on StackOverflow that I have searched for are not relevant or go unanswered.
Is this a supported feature in Team Services Online? What other steps can I use to diagnose and fix this problem?
Thanks in advance
The short of it is that this feature is not supported currently. More information here:
http://blogs.msdn.com/b/visualstudioalm/archive/2015/07/27/visual-studio-online-process-customization-update.aspx
Using Visual Studio Team Services and for some reason my changesets are being checked into the "Default Collection"...which contains the project this solution is a part of.
How do I make sure changesets are being associated with the actual project and not at the "level" above that?
As I mentioned in the comment its not possible to check-in files at the Collection level. You will get following error on doing that. Check your workspace mapping.
I want to use a .MPP MS Project 2007 plan which has not yet been mapped to work items in TFS, the TFS project is empty, I mean that there are no work items at all. I want to synchronize with http://localhost:8080/tfs/ so that I can transfer my entire business plan to TFS work items, but this is not working. I have tried doing this:
Open VS 2010 shell:
witadmin importwitd /collection:http://localhost:8080/tfs/ /p:"MyProject" /f:"Z:\task.xml"
but I still can't publish to TFS in MS Project, I get this error:
TF80006: Team Foundation needs a work item type to publish work items. Select a work item type for the work items you have added and then try again.
How can I fix this?
I have resolved this issue:
Download and install the Team Foundation Server Power Tools plugin for VS2010 here.
Under Tools > Process Editor > Work Item Types > Open WIT from Server to obtain the work item type from a TFS project on your TFS server. I selected "Task".
Publish again, this time edit the lines that have validation errors. The fields in yellow will have to be changed accordingly. Or, you can disable validation by following these steps.
One of gotchas that bit me was that I did not set the Work Item Type in Project. Once I set it to 'Task' I was able to publish my schedule to TFS.
I have an TFS server installation that through time has gone through upgrades from TFS 2005 to TFS 2008 and then to TFS 2010.
During the lifetime of the installation a lot of projects have been created and different project templates have been used. MSF Agile 4.0, 4.1, 4.2 and 5.0. and a few MSF CMMI ones.
What I would like to do is "replace" the project template used for all these projects to use a new one common one: Microsoft Visual Studio Scrum 1.0.
I am aware that TFS project templates are used as templates for creating new projects and cannot modify the tfs projects definitions after creation.
Uptil now only the version control and build server part of TFS have been used and there are no existing work item types.
Additionally all projects and build scripts are depending on the source code paths stay the same.
As I see it I have the following options:
Create new TFS projects using the correct project template and then move/branch the source code to the new project.
All code is moved to a temporary team project.
The old project is deleted
New project with the original name and correct process template is created
Code is moved to the new team project
Temporary team project is deleted
All the build definitions needs to be to recreated which is not an option.
The source code move/branch will "mess up" the versioning history
By messing up the versioning history I mean that when you move source code it will behind the scenes do a delete + source rename on the original location and the history will still be located in the old project. This will make searching in the history difficult and if I actually delete the old project I will loose all the history before the source code move.
This is really not an option for me since there is years of code change history that is needed to for supporting the different applications being built.
Use the TFS migration tools to migrate to another TFS project
This has the same downsides as the first solution
Replace/import work item types, install new reports, create new SharePoint sites
For each tfs project
Delete existing work item definitions using "witadmin deletewitd"
Import each work item definition from the new process template using "witadmin importwitd"
Import work item categories using "witadmin importcategories"
Delete old reports in project folder in report server
Upload the report definitions from the new process template
Modify data sources used for the reports using the report manager to point to the correct shared data sources (TfsReportDS and TfsOlapReportsDS)
Modify the report parameter ExplicitProject default value to "" (empty string) and disable prompt user option.
Export the documents in the old SharePoint site using stsadm
Delete the old SharePoint site
Recreate the sharepoint site using the TFS2010 Agile Dashboard site template
Activate site feature "Team Foundation Server Scrum dashboard"
In TFS Project Settings -> Project Portal Settings: Enable "team project portal" and ensure the url is correct. Enable "reports and dashboards refer to data for this team project"
And finally..
Process the Warehouse
Process the Analysis Database
Even though that this involves a lot of small steps this looks more appealing because
this option will not force me to move the source code and my existing build definitions will be intact.
My question:
Are there other ways to achieve the replacement of work item types that I haven't mentioned?
And/or am I missing any steps in last solution?
Given that you aren't using any existing work item types, your final proposal looks like the best option.
After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.
tfpt addprojectreports Add or overwrite reports for an existing team project
tfpt addprojectportal Add or move portal for an existing team project
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
Your first option is IMHO your best shot.
You can branch the sources from the old team project to the new team project. With TFS 2010 you can see the history also from the branched location. So you don't loose functionality in here.
The Build is just an msbuild file which is stored in source control. The only thing you have to do is actually copy the build definitions. You can do that either manually, or you can create a little app that does that for you.