I have the productivity power tools for visual studio 2010 installed on another computer that has VS2010 and it works great. When I received my new computer I added VS2013 to it and decided to install Productivity Power Tools 2013 as well as ReSharper. It has not gone well, the first time loaded a file and tried "find all references" VS went into an infinite loop with the scroll indicator moving up and down in a continuous cycle. After a week of work, the same infinite loop returned. Luckily, VS was able to recover my work (I now save often). Tabs no longer remain pinned. Where is the option to show pinned tabs on a separate row? I assumed that the Tools 2013 contained Tools 2010 but they do not work the same. I can't trust Tools 2013, so I disabled it. When I have the time I'll disable ReSharper and enable Tools 2013 to see if there is a conflict.
I really wish I could hide the pin on the custom document well. I keep it along the left side of the screen and pretty wide so my full filenames are always easy to scan and select. I absolutely never use pinning, and it takes up precious horizontal space in my editor.
Other than that, dang this is a great add on. Thanks team!
I really like the PowerCommand to "Remove and Sort Usings on save". I like clean code. There is one enhancement I'd really really like to see.
Allow the developer to exclude specified usings to not be removed. I have created some extension methods to the Exception class in a base class library. The methods are called DeepMessage and FullMessage that give me a nice readout of the messages from the exception and all inner exceptions. Usually I only use them in the debugger Watch window, rather than in the code itself. If no other code is used from the same class library namespace (a frequent occurrence), then the using statement gets removed when I save and the extension methods are no longer available within my debugger.
Installed this for the document well features. Used it for 5 minutes and did not care for the changes much. Uninstalled the extension.
This left my Visual Studio install in a broken state, Solutions take much longer to load, I eventually receive a popup from VS that an exception occurred. The solution explorer no longer displays the project tree.
Currently doing an install repair to try to fix it.
Really, really, unimpressed.
(I have Resharper installed, so the problem might be related to incompatibility with that, who knows)
Why are you guys changing the size of curly brackets ? The curly brackets looks smaller and it looks ugly after installing the power tools I disabled the "Column Guides", "Match Margin" and "Structure Visualizer", as a result the curly brackets are smaller and looks UGLY. Please... please fix it.
I've been working to upgrade a large Access Application to VB client / Postgresql Server. Installing the Productivity Power Tools 2013 broke my ability to Retrieve Data from the Server Explorer. VB crashed every time I right clicked to retrieve data from tables. Removing the Extension repaired the problem.
This tool set really is very useful because it makes working with the IDE more effective.
I found just one problem when I tried out the features:
For C++ code, the peek help is not very useful, because it always opens the generic help page
"Writing Code in the Code and Text Editor"
instead of the description for the selected word.
Peek help does work as expected and demonstrated on Channel 9 for C# files.
We have projects in Visual C# and C++. In Visual C# project, "Format document on save" feature works fine, files are properly formatted with tabs and spaces once we save the file, but when we try to do the same thing in Visual C++ project, it does not format the document. Is there any work around for this problem? or can you please provide fix for this issue?
I am developing a Port Monitor which write the printed file to disk as a PS file.
When I print a source (.cpp) file I get XPS document.ps instead of <filename.cpp.ps> which is what I would expect, and prefer. My Port Monitor grabs the file name from the Job Info for the print job, which works for most applications, including VS2013 without this extension.
Is there an option you can set that will achieve this, or is this a 'feature request' that I need to ask for?
I suggest that you show the dirty indicator in the custom document well tabs in front of the file name instead of after the file name. Now the indicator is not visible if the file name length exceeds the tab width.
In my case I have the tab width set to a fixed value of 180 (min and max equal). I often miss dirty files because I can't see the indicator.
When control clicking (if it's enabled) on nothing, there is an error. This is not necessary. It should not show anything. It is very intrusive and annoying to see a popup that contains no useful information at all.
Not showing a popup and simply not doing anything will be a clear enough indication that there is no definition to go to and it won't disrupt the programmer's flow.
Something I "really" need is to be able to print from the Diff window when it is in In-Line Mode.
This would be great for code reviews and keep track of your current changes, before they are fully commited.
It should be "easy" since the info is right there already merged... Just needs to be printed.
On a distributed app, sometimes whe need to add too many references from a project to another on the same solution.
Suppose I have the following scenario:
- ProjectB (References ProjectA)
Would be cool if we could drag the ProjectA inside the references folder of ProjectB to add a reference.
I know today is there an option to copy as reference and paste, but drag&drop will be more productive.
Nice job Guys!
I've been a using for this tool since VS2010, but this version crashes my VS2013 when I open/new a project.
The ActivityLog.xml shows the tool try to load from path "%APPDATA%\LOCAL\MICROSOFT\VISUALSTUDIO\12.0\EXTENSIONS\acmdzidq.sbe\CustomDocWell.dll", but the actual dll was in "APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\12.0\EXTENSIONS\uzh4nnvp.lax\CustomDocWell.dll".
I tried to re-install it, but no luck. Same error.