The issue over here is not related to the TFS Power Tools. Sebastin was under the impression that installing the TFS Power Tools would enable the Kanban board. However you need to update your TFS Server with at least Update 2. You can find the TFS Server Update 2 installation at http://www.microsoft.com/en-us/download/details.aspx?id=38185
Apparently something is wrong with the version detection on this package. I have vs 2012 web express edition and applied update 1 all on a newly configured machine. A prerequisites page comes up indicating that virtually all the features require "Microsoft Visual Studio 2012 or Visual Studio Team Explorer 2012". I have seen no mention of the power tools requiring the pro edition so I can only assume the detection criteria within the msi are incorrect?
Excellent set of tools to help with the upgrade to TFS2012. Using the TFPT commands to add reports to an existing team project without reports makes life a lot easier, along with Building the Team Site in WSS!! Thank you! These tools are required if you are using Visual Studio 2012 and TFS 2012 to have a completely satisfying experience with either product.
The install doesn't work in typical mode for starters, it mentions the data backup plan option needing to be installed on a server, then wont let you go any further.
Then try it in custom mode, and the shell extensions wont install alongside any other shell extensions, and I have to close it yet again.
This is going onto a fully patched Windows 7 x64 (Free) installation.
Hi, Sure this is a good tool and improve the work with TFS but it's strange nobody can tell why the process editor is not visible for several people. I still wait for feedback in FAQ.
This is the main reason i give only 2 stars as already essential parts (installation) does not work properly. brg axomoxoa
I have a mixed team of .NET and Java developers. The Java developers want to use the power tools to have the same functionality in Windows Explorer as they currently have with Subversion. My question is: do they need to install Team Explorer in order to work with the power tools? Or is Team Explorer Everywhere enough to give them that functionality?
To be clear: they will be using Eclipse and Team Explorer Everywhere. And they want the plugin in Windows Explorer.
I'm using TFS 2012 and I have some .tfignore files through the project to ensure certain things like build logs, etc. don't get checked in or added to source control.
Something I noticed is that if I right-click on a folder and select "Team Foundation Server -> Add..." that all the ignored files show up in the list of things I should/could potentially add.
I'm in a local workspace and following the instructions here: http://msdn.microsoft.com/en-us/library/ms245454.aspx
As ignored files get created, TFS doesn't seem to detect them as changes/adds (which is CORRECT) but I guess I also don't expect them to show up in the list of potential adds (which feels INCORRECT).
Am I missing something? Is this a TFS problem?
Hello,
we have moved from TFS 2010 to TFS 2012 and we are in need of updating process template.
When I try to open something from Open WIT from server menu. I receive:
The given path's format is not supported.
I am using Visual Studio prof 2012 with power tools 2012.
Peta,
When you "Open WIT from Server", we download the file into a temp folder. My assumption is that the temp location has invalid characters in it, and that is when we display the message.
You can work around this problem by manually save the WIT to a file with the "Export WIT" command. It are a few additional steps, but the result is the same.
Could you please verify that this works for you?
Installing on a machine with the TFS 2010 Power Tools installed yields this cryptic error:
"The TFS Backup Plan feature requires the TFS Application Tier to be installed. In order to continue, you must install TFS on this machine, or deselect the TFS Backup Plan feature."
Is there any plan to address this? The workaround is to go into Control Panel to modify the TFS 2010 Power Tools install to remove the Windows Shell Extensions component before installing the TFS 2012 Power Tools. Either making the installer do that automatically (preferred) or improving the error message to something relevant would be a step forward.
I am a bit confused on the version numbers you used. You say the TFS 2010 Power Tools, but do you mean the TFS 2012 Power Tools?
What version of Team Foundation Server do you have? If you have TFS 2012, then this is the correct Power Tools version. If you however have TFS 2010 installed, you can find the TFS 2010 Power Tools over here: http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f.
If you want to use the Backup Power Tool, you need to install it on the same machine as your Application Tier is installed (if you have a single machine setup of TFS, this is the server where TFS is installed).
Ewald Hofman
The use-case is the following:
TFS 2010 server (though I doubt this is relevant).
Visual Studio 2010, with TFS 2010 Power Tools, are already installed.
Visual Studio 2012 is installed. I now want to install the TFS 2012 Power Tools on this page. This is the use-case in which I receive this error.
Lest there be any confusion, the following page indicates that the download on this page should work with a TFS 2010 server, and the TFS Power Tools version (confusingly) corresponds to the Visual Studio version that it is to be used with.
http://blogs.msdn.com/b/bharry/archive/2012/09/15/tfs-2012-power-tools-are-now-available.aspx
I agree that it can be confusing. When you work with TFS, there are two moving parts.
The first one is the *server* object model. It lives on the Application Tier and does all the backend work.
The second one is the *client* object model. It lives on the client where Visual Studio lives, and hooks into the Team Explorer.
Some of the Power Tools (like the BPA) work against the server object model and need to be installed on the server. If you want to use the BPA, the version of the Power Tools must match the version of the TFS Server.
The majority of the Power Tools (like the Team Members) extend the Team Explorer window and needs to be installed on the Client, and thus must match the version of you Visual Studio.
In other words, if you have a Visual Studio 2012 and a TFS 2010 version. You install the TFS Power Tools 2012 on your client and the TFS Power Tools 2010 on the Application Tier.
Hopefully, this explanation clears the sky on the confusing version for you.
That all being said, now let's respond to the original issue. In your scenario you want to install the TFS Power Tools side-by-side to support Visual Studio 2010 and Visual Studio 2012. Although SxS installations are supported by Visual Studio, it is not a tested scenario for the Power Tools.
To be able to help you further, I would like to know what is it that you are trying to accomplish.
Thanks Ewald, that's great information. It's not always clear what features are part of the server vs. client object model, but the general distinction still helps.
I'm not sure if I could honestly tell you everything that developers on my team are using the TFS Power Tools for, but this post states (see reminder #5) that side-by-side install is supported.
http://blogs.msdn.com/b/bharry/archive/2012/09/15/tfs-2012-power-tools-are-now-available.aspx
We have TFS2010 server and VS2010 and VS2012 clients. Uninstalled VS2010 power tool client successfully. Installed 2012 PT successfully. I don't see the team members section.
The team members is rewritten for VS 2012 to make use of the new Team Explorer window. Unfortunately we have dropped the support for older TFS servers. If you want to use the Team Members with TFS 2010, you need to use VS 2010 and the TFS 2010 power tools.
Your other option is to upgrade your TFS server to 2012.
Sorry for not having a better answer
Ewald
1. In the Team Members functionality, please bring back the "Show Pending Changes" option. I often used this to clean up pending changes for workspaces that were no longer used.
2. Bug: If you've got a file checked out for edit, AND you have a lock on the file, the "Find in Source Control" window only shows "edit" in the "Change" column. However, in Source Control Explorer, the "Pending Change" column has the correct value of "lock, edit". Please fix "Find in Source Control" so that it shows "lock, edit" in this scenario instead of just "edit".
Hello RobSiklos,
1. Thank you for the suggestion, we will file it internally
2. Are you seeing this also for a Server workspace or this problem is only appearing on a local workspace?
I installed the latest version and, after rebooting to get the shell integration going, explorer.exe started taking up 10 - 20% CPU consistently and the disk became totally unresponsive. It took three reboots just to get Control Panel up and uninstall, then after the uninstall and another reboot my machine was back to being nice and responsive, no other changes.
That machine has:
* Windows Server 2008R2
* Visual Studio 2012
* Connection to a TFS 2012 machine
* No TFS source checked out
I never got to see any VS integration because I couldn't get the Start menu to come up... nor could I even do Start/Run and try typing anything. Total lockup.
I'm the current owner of the TFS shell extension. I'd like to look into the issue your seeing. Can you send a dump of any TfsShellExt entries in the Application Event Log to congyiw at microsoft dot com?
By "No TFS source checked out", do you mean that you have zero workspaces or that you have no pending edits? If you have workspaces, then:
* How many workspaces do you have, and on how many servers?
* Are these server or local workspaces?
* Approximately how many source controlled items are underneath the root of each workspace (I'm assuming they are rooted)?
* Approximately how many non source controlled items are underneath the root of each workspace (stuff created by build or hasn't been added for checked in)?
-Congyi
I will send you the requested event logs. Note I don't have it installed anymore so they're pretty generic "Event ID 3" sorts of things, but I'm sure you'll figure it out. The error (repeatedly) is "Failed to start COMProvider while calling CheckWorkstationCache."
By "no source checked out" I mean:
* I have one local workspace - the default one for the machine.
* I have nothing mapped in the workspace.
* I have nothing pulled down my local disk from any TFS source control. No source code on my machine from TFS. No artifacts. No nothing.
(Sorry, I tend to forget "check out" means something different in TFS than it does in *every other source control system ever*.)
Imagine you've never before connected VS to a TFS instance. You make that connection so you can open source control explorer and you get, by default, a local workspace for the machine. You've not mapped anything, you've not pulled down any source code. Then you install the shell extension. That's the state I was in.
If it makes a difference, I do have other source control plugins for the OS working - TortoiseSvn and TortoiseHg both work great.
Also, in case it matters, I run as a non-admin. I installed the power tools as a different user (a local administrator account) but my day to day work is as a separate, non-admin user. When I installed, I double-clicked the installer as the non-admin, got prompted for credentials, entered them, and let the installer run.
I have installed a fresh copy of TFS 2012 Update 2 on an application tier server along with VS 2012 Ultimate. I just installed the Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools but I cannot see any of the add-ins located within VS 2012 Ultimate on that server. The tools appear to be installed correctly under "C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools"; yet VS 2012 doesn't load the add-in like VS 2010 did. Any clue what might be wrong?
-Mick
Feel free to ignore this questions. After uninstalling the Power Tools, restarting, re-installing the Power Tools, and restarting the server I was able to see the Process Editor under the Tools menu. I believe that my problem was because I didn't install VS 2012 Ultimate BEFORE installing the Power Tools.
-Mick
You are correct. When you install the power tools, it checks whether you have the client (VS) and/or server (TFS) installed and selects the correct power tools based on that check.
If you want to know what power tools are installed, you can select the "Custom" setup type instead of the "Typical".
I am glad to see that you have resolved it yourself.
Ewald
Hila,
We released the Update 2 version yesterday. See also the announcement at Brian Harry's blog: http://blogs.msdn.com/b/bharry/archive/2013/05/08/tfs-2012-2-power-tools-update-available.aspx
Ewald
I tried to compare two build definitions with the TFS 2012 Power Tools. Unfortunately i always get the error message "could not load file or assembly 'Microsoft.TeamFoundation.Build.Workflow, Version=11.0.0.0, Culture=neutral, PublicKeyToken=....' or one of its dependencies. The system cannot find the file specified.". With a Team Foundation Server 2010 and the corresponding Power Tools 2010 it works fine. But it fails on a TFS 2012! I got this error on TFS 2012 Update 1 and for Update 2 as well. Can anyone help me out? Thanks in advance
Thanks for the report. I have filed a bug and I am following up with the owner of this particular feature. As soon as I hear something, I will update you.
