{"id":9741,"date":"2007-02-23T13:21:46","date_gmt":"2007-02-23T13:21:46","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2007\/02\/23\/yet-more-team-foundation-server-power-tools\/"},"modified":"2018-08-14T00:34:17","modified_gmt":"2018-08-14T00:34:17","slug":"yet-more-team-foundation-server-power-tools","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/yet-more-team-foundation-server-power-tools\/","title":{"rendered":"Yet More Team Foundation Server Power Tools"},"content":{"rendered":"<p>I went on vacation for a few days this week and lo and behold while I&#8217;m gone the team has released our next version of the TFS Power Tools (formerly Power Toys).&nbsp; We&#8217;ve numbered it Version 1.2 but I prefer to refer to it as the Feb &#8217;07 release.&nbsp; There&#8217;s a grab bag of new stuff in this release, including:<\/p>\n<ul>\n<li>2 new commands to the tfpt command line tool (use tfpt \/? to see details)<\/li>\n<ul>\n<li><strong>Workspace<\/strong> &#8211; Use the workspace command for additional workspace operations not supported in the currently shipping Team Foundation Server command line (tf.exe).&nbsp; Specifically, it supports a \/updatecomputer switch, that allows you to change the computer a workspace is associated with to &#8220;this&#8221; computer.&nbsp; This was added specifically as a result of feedback I got from someone reading my blog.<\/li>\n<li><strong>Treeclean<\/strong> &#8211; Use the treeclean command to see and optionally delete files in the current directory and all subdirectories that are not under version control.<\/li>\n<\/ul>\n<li>A new Process Template Editor.&nbsp; This tool is based on the work <a href=\"http:\/\/weblogs.asp.net\/Jsemeniuk\/\">Joel Semeniuk<\/a> has done but extends it to integrate with the Team Explorer, display a graphical view of the work item state diagram, handle a broader array of process templates, etc.&nbsp; This should substantially reduce the degree to which people have to munge around in XML files to edit work items.&nbsp; It&#8217;s by no means a complete Process Template editing solution but it&#8217;s a good start and covers the most common cases.<\/li>\n<li>A new test task for TFS Build that enables you to specify the DLLs that contain tests to be run rather than having to author a .vsmdi file.&nbsp; You may have see Buck talking about this on his <a href=\"http:\/\/blogs.msdn.com\/buckh\">blog<\/a>.&nbsp; This makes it much easier to mantain the list of tests to run during Continuous Integration or Nightly builds.<\/li>\n<li>A few checkin policies that enable commonly requested scenarios, including:<\/li>\n<ul>\n<li><strong>Changeset Comments<\/strong> &#8211; The Changeset Comments policy allows you to verify that the Comments text box in the Check In dialog box is not empty. You cannot check in a file if the Comments text box is empty.<\/li>\n<li><strong>Custom Path Policy<\/strong> &#8211; The Custom Path Policy works with existing Team Foundation Server check-in policies. &nbsp;It provides a mechanism that lets you specify the source control path or paths upon which a particular policy acts.&nbsp; This allows you toenforce a different sets of rules for different source control folders.<br \/>The Custom Path Policy also allows you to filter what specific items upon which a policy acts.&nbsp; For example, you can enforce an associated work item on check-in for files that end in &#8220;.cs, .sln, .csproj.&#8221;<\/li>\n<li><strong>Forbidden Patterns<\/strong> &#8211; The Forbidden Patterns policy allows you to specify a file extension or a regular expression that you can use to keep certain file types from being checked in to source control.<\/li>\n<li><strong>Work Item Query<\/strong> &#8211; The Work Item Query policy allows you to specify a team query to which the work item associated with a check-in must belong.&nbsp; If the results of the query do not include the work item associated with the check-in, check-in is blocked.&nbsp; This allows you to, for example, require that every checkin must be associated with an &#8220;active&#8221;, &#8220;approved&#8221; work item.<\/li>\n<\/ul>\n<li>Support for Windows Vista.<\/li>\n<li>The TFS Power Tools have been renamed from TFS Power Toys.<\/li>\n<li>Some misc bug fixes that I haven&#8217;t tracked down a list of \ud83d\ude42<\/li>\n<\/ul>\n<p>You can download the new TFPT release from <a href=\"http:\/\/go.microsoft.com\/?linkid=5422499\">here<\/a>\nI&#8217;ve already seen one problem crop up &#8211; uninstalling the old TFPT release on Vista.&nbsp; You get the error &#8220;Error 1721.&nbsp; There is a problem with with Windows Installer package. &#8230;&#8221;.&nbsp; You either need to disable UAC or you can run msiexec \/i tfpt.msi.\nI&#8217;ll try to post any other issues&nbsp;as I learn about them.&nbsp; Here&#8217;s a link to the <a href=\"http:\/\/forums.microsoft.com\/MSDN\/ShowForum.aspx?ForumID=930&amp;SiteID=1\">forum<\/a> where you can ask any question you have about the new release.\nWe had originally hoped to get this out in early December but a number of things conspired to make it take longer than we had hoped.&nbsp; As you can see there&#8217;s quite a bit of new stuff here and hopefully you will find it useful.&nbsp; Let us know what you think and what you&#8217;d like to see in future releases.\nWe&#8217;re already starting to plan what&#8217;s next.&nbsp; We&#8217;ve got a Vista sidebar tool already nearly complete and a bunch of other stuff in the hopper.&nbsp; We haven&#8217;t set a date yet but I&#8217;m hoping for something like April.&nbsp; We&#8217;ll see.\nThanks,<\/p>\n<p>Brian<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I went on vacation for a few days this week and lo and behold while I&#8217;m gone the team has released our next version of the TFS Power Tools (formerly Power Toys).&nbsp; We&#8217;ve numbered it Version 1.2 but I prefer to refer to it as the Feb &#8217;07 release.&nbsp; There&#8217;s a grab bag of new [&hellip;]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5],"class_list":["post-9741","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":"<p>I went on vacation for a few days this week and lo and behold while I&#8217;m gone the team has released our next version of the TFS Power Tools (formerly Power Toys).&nbsp; We&#8217;ve numbered it Version 1.2 but I prefer to refer to it as the Feb &#8217;07 release.&nbsp; There&#8217;s a grab bag of new [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/9741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=9741"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/9741\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=9741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=9741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=9741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}