Installing power tools kills explorer. Sometimes when I start up my computer Explorer crashes and restarts. Sometimes I boot with nothing but a black screen and a mouse pointer (no start menu, no nothing).
Uninstalling power tools fixes everything.
Based on other reviews, interference with explorer has been reported multiple times. I look forward to a fix so this package will be worth installing instead of being a huge waste of time.
I HIGHLY RECOMMEND THAT YOU DO NOT INSTALL TFS Power Tools if you often hibernate or sleep your computer. A few minutes after resuming your computer, TFS Power Tools will cause Windows Explorer to respond very slowly and often hang. Event Viewer will show hundreds of warnings and errors from TFSShellExt per minute since the time your computer was resumed. If you are quick enough you can open Task Manager and kill the TFS processes and wait a couple of minutes for Windows to return to normal, otherwise you'll have to restart your computer.
This problem has been discussed online and reported to the TFS Power Tools Team and still nothing has been done about it. Despite being a great tool otherwise, any productivity you would have gained by using it is voided by that nasty bug.
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!
Is there a release date for this same set of tools for Visual Studio 2015... Specifically the windows Shell integration, this is a fabulous tool and would love to have it in Visual Studio 2015.
Hope it can resolve previously reported "Made my system unuseable after resuming windows" issue. The "Windows Shell Extension" feature makes explorer.exe to eat a lot of memory after resume from hibernation.
Are there plans to support Visual Studio 2015? We've been relying on the comment checkin policy for years. Without a version for VS 2015, I have to override the checkin policy on every checkin, which to say the least, is getting old. FWIW we're still stuck on TFS 2012. We may be moving to TFS 2015 later this year assuming it releases by then.
Kim Carlsen - I have the same issue as you: Win8.1 pro, both 2013 update 2 and I can't clone. However I have a co-worker who has the option visible he upgraded from his 8.0 and also has 2012 installed.
The clone build option is missing for me on Windows 8.1 pro with VS2013 Ultimate and Update 3. I have the command line option and the Builds panel in VS is docked. I have tried on Windows Server 2012 R2 as well and the option is missing.
At this point it looks like a bug with the extension no longer loaded in Visual Studio. :-(
When I'm editing a Work Item Definition usually I use both Process Editor Extension and an Text Editor. If I change the .xml file of a work item, I want the VS detect that change and reload file, as they do with an .cs file for exemple.
Anyway, is possible to open source the TF PT source code? Or even just part of them?
The install runs without error, but when I look at extensions the TFS Process Template Editor and TFS Work Item Designer are there (but the icon is black and white, i.e. greyed out). And there is no entry for the actual TFS Power Tools VS2103.
Any help will be appreciated. I really need to get this working so I can clone builds. I have 10-15 that I have to created, and more to come in the future. Without cloning the process will take a lot longer.
I'm using Win8.1. VS2013 Pro. After installing version: 12.0.60919.00 and coming out of hibernation, my system was kept so busy with hard disk activity that I had to power off/on to get back it. I inspected the Event log and saw several TFSShellExt alternating Error/Warning messages per minute. I got work to do so I just uninstalled it, I do not have time to figure out why.
I'm seeing this too, first with Win8.1 RC then with fresh install of Win8.1. I'm pretty sure I saw it before with Win8.0, but not nearly so frequently. Explorer busies-out the CPU and gobbles all available memory; if you can get Task Manager open in time you can kill Explorer.exe and recover, but it's quite inconvenient!
The event log is full of TFSShellExt errors and warnings, just as Byron Adams notes.
This smells a lot like the problem brilliantly diagnosed and documented by Martin Kulov over two years ago, coming down to an incorrect implementation of the IDisposable pattern in TfsComProvider.Core.TfsCache.CachedServer, in which Finalize() calls Dispose(), but Dispose() is referencing managed objects that have already been cleaned up, resulting in a null reference exception:
I'm sure this specific bug has been fixed by now, but could there be something similar lurking in the codebase?
The same issue after resuming from hibernation these days. Even keyboard/mouse stop working. But I found Remote Desktop from other computer can change current desktop into login screen, and keyboard/mouse works there. (But the Remote Desktop client still cannot get into the desktop) I choose to restart at login screen. That's better than power reset...
I found a way to kill exploere.exe from remote computer, using
"taskkill /s (ip) /im explorer.exe" (From Windows 8) or "tskill explorer /server:(ip) /a /v" (from Windows 7). But I only use it twice, it seems need to connect Remote Desktop too...?
Just found this tool has update at 2014/4/3, but not seem from VS update notification... I have tried install new version and resume once... Not eating memory this time... Hope it's been fixed...
This tool update to 12.1.00402.0 at 5/13, but the download file seems just the same with previous one... And problem still the same...
I found another workaround, run msi - Modify - uncheck Windows Shell Extension (x64) then restart...
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...