Is there a way I can download and view the XML used to control my TFS Project? NOTE: I do not mean the standard template in TFS, but what is actually on the project (they don't match on my Server).
I want to see how some of the custom fields were put together.
Field definitions should be stored on the workitems themselves. You can use the Power Tools to export the work item type definitions and explore from there.
Power tools here:
Related
Looking for documentation about moving only a subset of contents from a TFS 2018 server in certain domain and hardware to another TFS 2018 server in another domain and hardware.
More Details :
It is possible to follow general instructions for migrating a tfs to another server/domain, but we need only a subset of the contents i.e. contents for specific team projects in the single default collection that we have. The existing documentation in microsoft docs relates only to all the contents as a whole. We'd thus also like to assess whats recommended : migrate all and delete relevant contents on target or migrate only relevant contents from source to destination. Contents include : code, work items, Build & Release, all history, etc...
There's no way split individual projects out of a team project collection without resorting to third-party integration tools and suffering from a lot of pain.
The best solution is to clone the team project collection using the standard process, migrate it, then delete what you don't want.
For a full-time TFS admin professional, about how many hours would go into "customizing" an existing scrum template project to add an additional work item type?
The easiest way to add a new WIT is to copy an existing WIT and then modify the definition file. You have two options to achieve it:
You can install TFS Power Tools, this tool provides an add-in to the Team menu and a new section on the Work Items page in Team Explorer. Use this tool to create new work items with default values, or to easily apply values to existing work items.
You can export the a WIT definition files, and edit it, then import it. Useful links:
https://www.visualstudio.com/en-us/docs/work/customize/add-modify-wit#add-wit
https://msdn.microsoft.com/en-us/library/ms404855.aspx
Regarding how many hours it will cost, it depends on your detailed requirement and whether you are familiar with TFS Power Tools and WIT definition files. If you just want to create a new WIT based an existing WIT, and just add some field, it will only need several minutes with TFS Power Tool.
I have database script folder in TFS.Developers add and changed the script files. I want to generate single text file when I specify the two change sets. Is there any possibility doing that in TFS 2010.
You can use the TFS API to query the code history, and pull out the data that way (you'd have to write the code to do this yourself).
The better way to manage updating databases is to use a Visual Studio Database Project (aka SSDT) and let the tooling do this for you.
How can one determining which TFS process template is being used? A few were installed and now I can't determine which one is being used by TFS.
TFS Team Project Manager on CodePlex is a free tool which will inspect all your team projects process templates (even if they're customized) and tell you which process template was most likely used to create that Team Project (and give you a % confidence in the match). You can even give it additional "source" process templates, such as your company custom process template, and it will tell you which projects were created with it.
In addition to Edward's approach:Another one, quick & dirty and without any capability to reveal any changes you might have performed, is the following:Right-Click on your TeamProject from within the Team Explorer and select "Team Project Process Guidance":
This should pop-up a webpage that will show you the Process Template that was used to create it.
If you have not modified the process templates (either the ones that are included with TFS, or any that you might have downloaded and installed) then you can export the process template as an XML file and compare against the original version.
(That link is really about modifying the process template, but steps 1-3 discuss how to export the current process template for a Team Project.)
Of course, even if you had modified the process templates slightly, using a diff tool may be able to yield results as to which process templates those were derived from.
We're currently setting up a number of builds in TFS2010 for our various projects/solutions.
We have a large number where the structure and paths, etc. are essentially the same, but one word may change (for example, using all Integration workspaces versus our Trunk workspaces).
In TFS2008, I would simply edit the XML directly and do some creative search and replace or some magic in textpad before saving the file. However, I do not see any immediate way of doing this in TFS2010 - so I'm stuck slogging through the build definition UI.
I know, in doing a SQL Trace, that all of this ends up as XML - so is there a way to directly access this XML for hand-editing vs. being forced to do all changes through the front-end?
Thanks!
Edit for additional clarity
I have the Power Tools installed, etc. and can clone my builds - but my editing options are still limited to the UI, so if I have a large number of workspace path changes I have to do them by hand (one at a time).
My goal is to be able to directly edit the XAML for a specific build definition so I can do a clone, open the XAML, and then do a search/replace in bulk.
Download and install the Team Foundation Server Power Tools. You can also get them through the Visual Studio Extension Gallery. After installing, you can right click on a Build Definition in Team Explorer and select the Clone Build Definition command (added by the Power Tools installation) to make a copy of an existing build definition. Then you can tweak it appropriately for another branch, etc.
The following tool (VS Addin) will satisfy your requirement>
Community TFS Build Manager
http://visualstudiogallery.msdn.microsoft.com/16bafc63-0f20-4cc3-8b67-4e25d150102c
The build definitions are all .xaml files now - they're WF4 workflows, and they're XML files.
Jim Lamb is right. The build templates are .xaml files now. The definitions are accessed through web services.
I'm about to experiment with a quick HTML form posting to /tfs/_tfs_resources/Build/V3.0/BuildService.asmx/QueryBuildDefinitionsByUri. I noticed when I clicked the build definition in Team Explorer that it has an associated URI: vstfs:///Build/Definition/2. Stay tuned.