Whilst the functionality is useful, this plugin invariably causes Windows Explorer (explorer.exe) process to run at 100% CPU, effectively rendering the PC unusable until Explorer is killed. Whatever the problem, it needs to be fixed.
When I installed VS 2013 and did not find the clone build and wildcard find option I wasn't happy at all. These are nice little productivity tools. TFPT provides that and a lot of other work item modification capabilities. A must have for any TFS Admin!
Complete error is "The Windows Shell Extension component cannot be installed side-by-side with previous versions. In order to continue, you must deselect that feature, or cancel this installation, uninstall the previous Windows Shell Extension and restart this installation.
Can someone tell me what to look for to uninstall?
I manage a TFS project that has several teams created. (since I manage, I am admin on all teams)
User 1 (me)
User 1 (me)
User 1 (me)
The problem is on a single team, when I select Team A and click the Team Members button, I am taken to the Team Members view, but the only team member is a member of an entirely different team, User 3.
Now, to confuse me further, when I go to User 2s machine, and look at the Team Members view, he sees a single user also, but the user he sees is User 7.
If I select one of the other teams which I am a member, I see the correct listing of members as I would expect. It is only this single team which does not display the correct users.
Without knowing what else to do, I have clear VS cache, and restarted VS, but the problem persists.
Is this bug, or is there something else I can try to fix this?
Follow-up: As a last ditch effort I deleted the team then recreated it.
Now I see some other random person in the list, only this time, it is someone who does not belong to any of the teams within this project.
Did I mention how annoying this is?
If I disable the following setting in TFS 2013:
TEAM / Team Project Settings / Source Control / Check-out Settings / Enable multiple checkout
multiple checkouts are prevented when using the source control explorer but they are still possible if I check-out a file in the Windows Explorer using TFS 2013 Power Tools.
Is this a bug or have I missed some additional settings?
Thanks for this power tools. Recently I'm trying VS2015 Preview. The only problem stop me from using it regularly is it doesn't support our TFS's "Custom Path Policy". So please release a new version for VS 2015 Preview...Thanks... Or you can open source it like others too...
I'm getting an
"1721 Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run."
when I try to install the tools on the TFS server machine. I've spend hours researching this, and have found several suggestions that do not work. The tools installed fine on my Win 7 x64 workstation. The server is also running on Win 7 x64. Both machines are almost identical (same MB, etc.), the only difference being my workstation has 32 GB of ram and the TFS server having only 16 GB. All OS patches are installed on both machines.
One suggestion I have not been able to try is to install tfpt.msi directly (as opposed to installing the download from this site); I have not been able to find that file.
Where can I get the tfpt.msi file? Or if that's not the solution, do you have another suggestion?
Microsoft Team Foundation Server 2013 Power Tools
add more than 150 chars to PATH (on Windows7x64):
C:\Program Files (x86)\Microsoft Team Foundation Server 2013 Power Tools\
C:\Program Files (x86)\Microsoft Team Foundation Server 2013 Power Tools\Best Practices Analyzer\
are these really needed?
would it be ok to shorten them with symbolic links?
I want to add WorkItemQueryPolicy through a homemade program.
Now I can add the WorkItemQueryPolicy but I don't know what to set the verification query.
Is it possible to set the verification query using the c# code.
I'm unable to run the Best Practices Analyzer on a TFS Instance with Update 3.
I'm getting the following error:
Error (Rule name 'DoConfig_szConfigDBProductVersion' referenced by rule 'DoConfig_InstanceHealthCheck_TpcSQLGetSQLDBInfo_fDBVersionIncorrect' in input file is not defined) in format of rules in configuration file.
I think the problem is due to one of these options:
- The TFPT is in Update 2 and I'm running it into an Update 3 instance;
- The TFS is installed on a SQL Server 2014, which may be not compatible.
Has anyone had this issue either?