{"id":8231,"date":"2007-12-21T20:00:20","date_gmt":"2007-12-21T20:00:20","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2007\/12\/21\/december-07-release-of-the-tfs-power-tools-for-tfs-2008-are-available\/"},"modified":"2018-08-14T00:27:39","modified_gmt":"2018-08-14T00:27:39","slug":"december-07-release-of-the-tfs-power-tools-for-tfs-2008-are-available","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/december-07-release-of-the-tfs-power-tools-for-tfs-2008-are-available\/","title":{"rendered":"December &#039;07 Release of the TFS Power Tools for TFS 2008 are Available!"},"content":{"rendered":"<p>Today we released the first version of the Team Foundation Server 2008 Power Tools.&#160; This new release is primarily intended for use with a VS 2008 client.&#160; All VS integrated components with this new release will only integrate with VS 2008.&#160; Power Tool features in this release require that the Team Explorer 2008 be installed.&#160; Those features that do not integrate directly with Visual Studio (e.g. command line tools) can easily be used in concert with VS 2005 development.&#160; The <a href=\"http:\/\/msdn2.microsoft.com\/en-us\/teamsystem\/aa718351.aspx\">TFS 2005 Power Tools<\/a> are still available for the VS 2005 client.&#160; <\/p>\n<p><u>Download URLs<\/u><\/p>\n<p>Power Tools: <a title=\"http:\/\/msdn2.microsoft.com\/en-us\/tfs2008\/bb980963.aspx\" href=\"http:\/\/msdn2.microsoft.com\/en-us\/tfs2008\/bb980963.aspx\">http:\/\/msdn2.microsoft.com\/en-us\/tfs2008\/bb980963.aspx<\/a><\/p>\n<p>MSSCCI Provider update: <a title=\"http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyId=FAEB7636-644E-451A-90D4-7947217DA0E7&amp;displaylang=en\" href=\"http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyId=FAEB7636-644E-451A-90D4-7947217DA0E7&amp;displaylang=en\">http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyId=FAEB7636-644E-451A-90D4-7947217DA0E7&amp;displaylang=en<\/a><\/p>\n<p>There are many new features\/updates in this release.&#160; They include&#8230;<\/p>\n<p><strong>MSSCCI Provider<\/strong> &#8211; We&#8217;ve updated the MSSCCI provider (that enables TFS access from VS 2003, VS 2002, VS 6 and a host of other IDEs) to use the TFS 2008 object model.&#160; In the process we&#8217;ve fixed as many bugs that have been reported as we could.<\/p>\n<p><strong>Build Notification Tray app<\/strong> &#8211; We&#8217;re releasing our first Power Tool version of the build notification tray app.&#160; This tool allows you to monitor the current status of automated builds easily.&#160; You can be notified immediately when a build fails (or succeeds even) so that you can address it promptly.&#160; A failure notification will appear like&#8230;<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/brokennotification.png\" \/><\/p>\n<p>From which you can easily navigate to the build status window which allows you find out more info on the build.&#160; Or you can go to the changesets\/workitems that are in the build.<\/p>\n<p><strong>Process Template Editor<\/strong> &#8211; In addition to hosting the Process Template Editor in the VS 2008 IDE, we&#8217;ve made bug fixes and small improvements.&#160; They include:<\/p>\n<ul>\n<li>Making it more discoverable by moving it to the VS Tools menu <\/li>\n<li>Substantially improved the performance &#8211; particularly when there are many states <\/li>\n<li>Fixes for all of the serious bugs that users have reported. <\/li>\n<\/ul>\n<p><strong>Best Practices Analyzer<\/strong> &#8211; The Best Practices Analyzer is a tool we first released in September that is designed to help diagnose problems with TFS installation and help you quickly correct them.&#160; In this Power Tools release, we have updated it to support TFS 2008 and the wide array of additional configurations that TFS 2008 supports.<\/p>\n<p><strong>Status Search and Wildcard Search<\/strong> &#8211; By popular demand, we have added features roughly equivalent to Status Search and Wildcard Search in SourceSafe.&#160; These features allow you to search in the Source Control Explorer to find files by wildcard and\/or checkout status.&#160; Further, you can operate on the search results, including (assuming you have the necessary permission), undoing checkouts in other people&#8217;s workspaces.&#160; You&#8217;ll find the &quot;Find in Source Control&quot; sub menu in the File -&gt; Source Control menu and the right click menu when looking at the Source Control Explorer.<\/p>\n<p>The search dialog looks like:<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_2.png\"><img decoding=\"async\" style=\"border-right: 0px;border-top: 0px;border-left: 0px;border-bottom: 0px\" height=\"162\" alt=\"image\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_thumb.png\" width=\"244\" border=\"0\" \/><\/a> <\/p>\n<p>The search results look like:<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_4.png\"><img decoding=\"async\" style=\"border-right: 0px;border-top: 0px;border-left: 0px;border-bottom: 0px\" height=\"399\" alt=\"image\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_thumb_1.png\" width=\"644\" border=\"0\" \/><\/a> <\/p>\n<p>In addition to these new commands, we&#8217;ve put a menu option for the difficult to discover &quot;Find Changeset&quot; command on the same submenu so that all of your &quot;find commands&quot; in TFS are in one handy place.<\/p>\n<p>In case you want to bind key combinations to them, the commands are:<\/p>\n<ul>\n<li>File.TfsContextSceStatusSearch<\/li>\n<li>File.TfsContextSceWildcardSearch<\/li>\n<li>File.TfsContextSceChangesetSearch<\/li>\n<\/ul>\n<p><strong>Navigate to Windows Explorer<\/strong> &#8211; We added a menu option in both the Find in Source Control results and in Source Control Explorer to navigate easily to the corresponding folder in your workspace using Windows Explorer.<\/p>\n<p>In case you want to bind a key combination, the command is:<\/p>\n<ul>\n<li>File.TfsContextWindowsExplorerLaunch<\/li>\n<\/ul>\n<p><strong>Quick Label<\/strong> &#8211; A very simple label dialog that everyone has been asking for that enables you to easily label a file or folder and all its contents at a point in time.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_6.png\"><img decoding=\"async\" style=\"border-right: 0px;border-top: 0px;border-left: 0px;border-bottom: 0px\" height=\"326\" alt=\"image\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_thumb_2.png\" width=\"426\" border=\"0\" \/><\/a> <\/p>\n<p>In case you want to bind a key combination, the command is: <\/p>\n<ul>\n<li>File.TfsContextQuickLabel<\/li>\n<\/ul>\n<p><strong>Work Item &amp; Work Item Type Destroy<\/strong> &#8211; We have added support to the tfpt command line to enable permanent deletion of work items and work item types.&#160; We added server side support for it in TFS 2008 but did not have time to get the client side support done.&#160; So until that makes it into an official release, that support will live in the Power Tools.<\/p>\n<p>tfpt destroywi \/server:tfsservername \/workitemid:value1[,value2,&#8230;]<\/p>\n<p>tfpt destroywitd \/server:tfsservername \/project:projname \/workitemtype:witdname<\/p>\n<p><strong>New configuration command<\/strong> &#8211; We added a new command called tfpt tweakui to make it\n much easier to configure connection properties &#8211; like client certificates for HTTPS, etc.<\/p>\n<p><strong>Removed Features<\/strong> &#8211; A few Power Tool features have been removed because they were incorporated into the 2008 version of Team Explorer.&#160; Examples include Annotate and Folder Difference.<\/p>\n<p>I hope you are as excited about these new features as I am.&#160; It&#8217;s another great increment of features on top of the base TFS product.&#160; We continue forward with our commitment to deliver value regularly.&#160; Our rough target is to deliver Power Tools with new features, bug fixes, etc every 3 months.&#160; Many of the Power Tools will be picked up into &quot;official releases&quot; as time allows.&#160; Please let us know what you think of this release and anything you&#8217;d like to make sure we do soon.<\/p>\n<p>Thanks,<\/p>\n<p>Brian<\/p>\n<p>P.S. If you are looking to the Database Professional Power Tools, they are not in this download &#8211; these are just the TFS Power Tools.&#160; I believe the 2008 compatible Database Professional Power Tools will be available shortly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today we released the first version of the Team Foundation Server 2008 Power Tools.&#160; This new release is primarily intended for use with a VS 2008 client.&#160; All VS integrated components with this new release will only integrate with VS 2008.&#160; Power Tool features in this release require that the Team Explorer 2008 be installed.&#160; [&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-8231","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":"<p>Today we released the first version of the Team Foundation Server 2008 Power Tools.&#160; This new release is primarily intended for use with a VS 2008 client.&#160; All VS integrated components with this new release will only integrate with VS 2008.&#160; Power Tool features in this release require that the Team Explorer 2008 be installed.&#160; [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/8231","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=8231"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/8231\/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=8231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=8231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=8231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}