background preloader

TFS

Facebook Twitter

$log$ / Keyword Substitution / Expansion Check-In Policy (TFS - LogSubstPol) Reusable Project And Item Templates using Visual Studio and XML. Visual Studio 2005 Create Reusable Project And Item Templates For Your Development Team Matt Milner Code download available at:CodeTemplates.exe(139 KB) Over my years of working with clients on building Microsoft® .NET Framework-based applications, I have often heard a common feature request for Visual Studio® .NET: "It would be great if we could create our own project types and item types so that all developers in our organization would have access to them. " Many orgs want to create shared templates for projects such as Web sites or for project items, such as a default Web page or forms. Visual Studio 2005 introduces a new model for defining templates and starter kits for projects and items that make this not only possible, but relatively simple.

I'll take a look at how to consume, create, and customize these templates. Consuming an Existing Template The easiest way to understand how these templates work is to first take a look at how to consume a template that has already been created. Using System Fields and Fields Defined by the MSF Process Templates. By using the index of fields in this topic, you can look up a description of each field used to track work items. This reference includes all fields defined within the default process templates for Team Foundation Server (TFS). You use two main types of fields to track data for a type of work item. System fields are defined for all work item types, and all other fields are created by adding FIELD element definitions for them to a work item type. When the work item type is uploaded to Team Foundation, either when a team project is created or by other means, all new fields are added to the set of fields that are defined for the team project collection. For example, when you create a team project that uses the process template for Microsoft Solutions Framework (MSF) for Agile Software Development, all fields that are defined in each Agile work item type are added to the team project collection of data fields.

TFSFieldMapping. Team Foundation Server Administration Tool. The TFS Administration Tool allows Team Foundation Server administrators to manage user permissions on all three platforms utilized by Team Foundation Server: Team Foundation Server,SharePoint, andSQL Server Reporting Services. The tool also allows administrators to easily copy user permissions among team projects and to easily identify any missing permissions on any of the three platforms. Announcements December 16, 2013-TFS Administration Tool 2.3 releasedWe are pleased to announce that the TFS Administration Tool 2.3 has been updated to the Team Foundation Server 2013 object model and it can be installed on machines running either the stand-alone object model or Visual Studio 2013.

This release supports SharePoint groups/roles. There are no other major functional changed between the release and the previous (2.2) release. It is not required to uninstall the previous (2.2) release. Please download TFS Administration Tool 2.3, and let us know what you think about the tool. Project field mapping questions. TFS Top Tip #3: Removing the Resolve Check-In Action from a Work Item - Martin Woodward.

I don’t know about you, but I love associating my check-ins with work items using the Pending Changes view, it makes it so easy to maintain requirements traceability and helps me feel less guilty as I’m doing one more thing that I should have been doing for years. The only problem with the default definitions for Bug and Task are that if you select the item then by default the “Resolve” check-in action is selected. This is annoying for me as it the action I want to take in probably about 5% of check-ins. 95% of the time I just want to associate and 90% of the time I forgot that I have to change the default setting and end up going back to the work item and re-activating it.

The “Resolve” option is displayed when a state transition in the work item’s workflow is defined as having an action defined for check-in. Below is the transition section from the MSF Agile Bug:- How to: Download or Upload a Microsoft Project Field Mapping File. MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development Online Services patterns & practices Servers and Enterprise Development Web Development Download or upload a Microsoft Project Field Mapping file Other Versions This topic has not yet been rated - Rate this topic This topic has been merged with the TFSFieldMapping command topic, Upload or Download the Microsoft Project Mapping File [TFSFieldMapping].

Show: © 2014 Microsoft. Undocumented attributes for controlling the Work Item form layout - TFS & Visual Studio ALM - by Neno Loje. Naren [1] revealed a few very interesting on hidden attributes his blog [2] which you definitely should take a look at since they let you solve some problems as the following ones: Control the height of two text boxes that were placed vertically on one tab When placing more than one text box on a tab page you will notice that all text boxes have the same height except the last one which can be annoying if you use HTML and expect the writer to write a lot. Using the “MinimumSize” attribute in the Work Item Type XML you can specify the minimum width and height that the control has to have.

Resulting in a much more nice looking writing experience: Show the same field twice in different places Sometimes it makes sense to place the same field on two places for example in the general area as well as on a tab. So here’s the background by Naren. . [1] TFS & Visual Studio ALM - by Neno Loje. Visual Studio Online (VSO) vs. Team Foundation Server (TFS) This blog post is comparing the current feature set of Microsoft's hosted TFS solution – Visual Studio Online (VSO) and the on-premises Team Foundation Server product. Feature Comparison (as of February 2014) Remember: Visual Studio Online is currently a so-called “commercial preview”. Some other limitations of VSO (as of February 2014) No Data Export (there are plans to make it available for a short time period) No Data Import (if you want to move from on-premises TFS to VSO) No Integration with Active Directory (users sign in using Microsoft Accounts) No choice of geographic location (data stored in data center in Chicago) --Neno When to use the Test Attachments Cleaner (and when not) What is the Test Attachment Cleaner?

A command line tool that only removes the attachments. You need to Test Attachment Cleaner if you: You do not need the Test Attachment Cleaner if you: Where do I get it from? The Problem The Solution Good luck! Answer: Work Item Customization tidbits (part 1 of X) One of the typical TFS administration task is Work Item Template customization. Chances are, even if you never did it sooner or later you will. However, while work item customization is often represented as very simple activity there is a host of things not to do and also quite a few useful tidbits of information helping to make customizations easier. Over the (three) years that I am working with TFS I have my little arsenal of tricks and I was meaning to make it public for a while. It does not mean to replace the guidance on MSDN but rather to provide less formal description of the things that matter in my opinion. The intended audience is not a seasoned TFS administrator that knows intimately the syntax and what can/cannot be done with it but rather a person who starts designing templates from scratch or contemplating changes to existing ones.

If you want to use work items, there are a few choices For the last two scenarios the work item type templates will have to be customized. James Manning's blog. David Gardiner - Dave's Daydreams: Setting TFS work items to default to be unassigned. Wouldn't it be nice to have your work items in Team Foundation Server default to be "unassigned", so that it is easier to determine what jobs are being worked on and what are unallocated? Well it turns out this is possible. First of all, you need to export the work item definitions that you want to customise: cd "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE" witexport.exe /t tfsserver /p ProjectName /n Bug /f c:\Bug.xml witexport.exe /t tfsserver /p ProjectName /n Task/f c:\Task.xml Now open these .xml files, locate the "Assigned To" field and update it to be the following: <HELPTEXT>The person assigned to do the work</HELPTEXT> What this does is limit the users that are displayed in the "Assigned to" drop-down list box to be just the direct project administrators and contributors.

Import these back into TFS: witimport.exe /t tfsserver /p ProjectName /f c:\Bug.xml witimport.exe /t tfsserver /p ProjectName /f c:\Task.xml. VSTS Team Explorer Known Issues. Controls | Silverlike - A Free Microsoft Silverlight 3 Directory. TFS 2008 Problem with Area/Iteration after Doing a Move. After making a modification to Areas/Iteration, these changes does not show up when creating a new Workitem. You reboot the TFS and close/reopen Visual Studio client, but the changes won't effect to work item. This was a recent upgrade from TFS2005. The following entries were missing in the TFSintergration->tbl_subscription table in the TFS SQL database: 1,BuildCompletionEvent,,<sid>,0,2, 2,DataChangedEvent,,<sid>,0,2, 3,ProjectCreatedEvent,,<sid>,0,2, 4,DataChangedEvent,,<sid>,0,2, Use the BisSubscribe tool to fix this problem.

This command line tool is located at <drive>:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\TF Setup.