It would have made me MUCH more productive if it had said on this site that the tools are ONLY supported by VS2013 *professional* and above.
I've no problem with upgrading to the Pro edition *BUT* right now VS2013 is so SLOOOOOOOW to start any debugging session (and there are DOZENS of different reasons for this, I've yet to find the one(s) that apply in my case) and I'm reluctant to shell out for the Pro version until I'm satisfied it's actually useable. I was hoping the productivity tools would help me pinpoint the issue. As it is I've wasted so much time trying to work out how to install them - and discovering they're knackered - that by now I could have actually started a debug session! :-(
Beats me why Microsoft blow trumpets about how great VS is, then feels the need to release a "productivity" pack (for free) which doesn't actually work with all versions.
It was actually a missing piece of Visual Studio: why not embedding by default? Very nice the structure visualizer, although I'd use less opaque colors for the outlines (either a pastel-shade, or a 50% opacity). I'd also provide some kind of highlight for the structure popup: maybe a drop shadow? Excellent idea on squeezing the less-important rows! Also very noticeable are the error tracking, and the scrollbar markers.
The point which disappointed me was actually on the print capabilities. I found this package right because I wanted to print a section of a module, without the tedious copy+paste on Wordpad, which preserves the formats very well. Why not providing a preview, such as IE offers? In order to avoid to waste paper, I'd find very useful the ability to inspect what are the useful pages, and/or adjust some parameter.
Anyway, the product deserves a five-star rating without any doubt! Thanks, and go further!
Some tools are very useful and handy, others less so, but overall it's a great collection.
* Double-click maximizing does not preserve collapsed state and causes tab reordering when a window is collapsed after being restored. * There are a lot of options for customizing document tabs, but still no option for multiple horizontal rows. It's compact (unlike vertical tabs), it displays all documents (unlike horizontal tabs) and it's a basic functionality of a tab control. * Code structure in the margin is a good idea, but with no options to customize display, even colors, it's useless. In a big file with many classes and methods, it's hard to distinguish thin class lines and wide method arcs become thin as well. Just open Dictionary<,>'s source file and you'll see. * Code structure previews waste space on attributes making class names invisible. Again, open Dictionary<,>'s source file. * Default colors for projects look weird in VS light theme. I don't get why they are dark.
Good for removing & sorting using statements across project or entire solution. Also provides a good mechanism for opening a command shell at the project directory, but doesn't provide the same for PowerShell
It is great extension with lot of features and commands, but still I find it lacking because it does not have the following feature. I cannot find any extension which does that, but the team who developed this could definitely do it.
Whenever I open a new file from solution explorer, it puts that file as the first tab in document well. But as I keep opening files, they just go into overflow list. But what I am looking is that whenever I open a file from solution explorer, even if it is already in document well (or overflow list), it should put that file as the first tab. This way I always have my most recent files at first so that I can easily switch. The existing sortings are always by project or alphabetical, but most of the times, the files you want to use may not be in that order. Thanks.
This is an old problem I already had in VS 2010, and which hasn't been solved yet it seems.
The [ key is reassigned to the align assignment function.
I wouldn't assign anything on a key that might be useful when typing C#/C++ code, the open bracket is used for arrays which are part of those languages.
I'm using pretty well the stock settings for most things, and when I save (generally using [ctrl]+[s] or my personally mapped [ctrl]+[shift]+[s] (save all)) it won't always remove the dirty indicator on the file.
It seems particularly fond of leaving the currently open document "dirty" when "Save-All"ing, but it goes either way.
Right now I tend to hit save until it does go away, just to be safe, but it would be nice to not have to.
I love this extension, though; I've used it in every install of every version of VS I've ever used.
Upgraded to Visual Studio 2013, Update 3. Upon restarting Visual Studio, it appeared that Presenter mode was turned on, but when I tried to execute the PresentOff quick task, I got an error message saying that presenter mode was not on.
Ended up having to reset the environment fonts via Tools>Options, but have been unable to get the Properties window fonts to reset.
After resetting the environment fonts, presenton and presentoff are working again, with the exception of the Properties window. Which (with the exception of the title bar font) is not responding to these quick tasks at all.
I appear to have the latest version of the Productivity Power Tools installed. Any suggestions for resetting the Properties window fonts?
And it gets a little weirder...tried restarting Visual Studio to see if that would resolve the issue, and it did reset the Properties window font to the default size. But now if I turn presenter mode on, everything else gets larger fonts, EXCEPT the Properties window.
1) After working extensively with VS 2013 and frequently using "Peek Definition" on various symbols, the pop up frame may eventually become empty; most likely due to out-dated intellisense data. It will NOT display the error message "A definition for the symbol 'xxx' could not be located."
2) Hit ESC to dismiss the empty pop up frame.
3) Invoke peek definition again on a symbol.
> Visual Studio crashes with an access violation exception.
The incomplete or aborted intellisense query apparently left the module in a mal-formed state.
Sorry you've been hitting this issue. To follow up more effectively on this, it would help if you could raise a bug on Connect at https://connect.microsoft.com/visualStudio/ marking the title Productivity Power Tools 2013 - Crash in Peek. We need to capture a crash dump for the issue so we can see where the failure is.
The Visual Studio Feedback Tool (http://visualstudiogallery.msdn.microsoft.com/563d1003-f0ed-498f-8ef9-f8ee1aac39fe ) makes it really easy to file Connect bugs with the right data, including capture of crash information.
Program Manager, Visual Studio Editor Team
a while back, productivity tool use to support color coding the output panel. although there is another extension we can use for that purpose, but i wonder would this feature ever being bring back ?
Hi guys, I love this, running vs2013 but with all the extensions enabled and running ankhsvn, if I rename a file (that is already committed to the repo) I get a COM error E_FAIL.
If I disable all the individual productivity modules in options I can rename the file but I get an error when trying to check it in (so there is obviously some residual disruption from the plugin)
If I disable productivity power tools entirely it works normally.
I understand it may be something that ankh is doing but I wanted to bring to your attention just in case. Of course, I can do without power tools, but not without source control.. so I have to keep this disabled for now :(
running AnhSVN v2.5.12471.17
Productivity Power Tools v12.0.30519.1
After this is installed (VS 2013 prof) I am unable to 'Copy' anything.
Invalid index. (Exception HRESULT: 0x8002000B
I have tried rebooting, reinstalling. Goes away as soon as its removed. Any ideas?