Quite useful but also contains some serious flaws!
Watch out for the options: 1) "Enhanced Scroll Bar" - this can slow the editor down to a crawl at times.
2) In "Tabs and Windows" - do not check "Maintain pin status if document is removed from well"! It causes DevStudio to crash when doing routine operations like running up an app in the debugger, or lock up with resizing the main window. If you are getting faulting module: KERNELBASE.dll with exception code 0xe0434352 in DEVENV.EXE reported to your EventLog, then there is a good chance that it is this option!
Unfortunately, this 2012 version is missing the superb functionality from 2012 the Ctrl+2 to quickly navigate to any class/member in the current source file. This is a pain, because now to navigate to class/member in current source file, one must reach to the mouse and use either solution explorer or the combobox menu, none of these is as quick and elegant as was the keyboard only popup solution with CTRL+2 in PowerTools 2010 version.
I have been a Microsoft fanboy for my entire programming career, but 2012-2013 may be your (Microsoft's) downfall. Everything is pushed out without QA - Win8, Office2013, VS2012, and now this update. Have you ever heard of saving configuration settings??? Now I've got to go waste an hour to figure out what my settings should be. AGAIN.
My team has StyleCop enabled with requirements that the 'System' using directives be placed above all others (Rule SA1208).
Is there a way to have the 'sort usings' functionality sort in this way? If not, please consider adding it.
hi folks - I've installed the Productivity Power Tools. I can access many of the new features but the new Solution Navigator is nowhere to be seen. Do I need to do something to enable this functionality?
The new solution explorer in vs 2012 is way more behind the solution navigator included in the power tools. you cant expand members, like methods, and cant navigate to the local variables, which was extremely useful in a long method. The only improvement is the preview selected items.
It would be nice to see the solution navigator back in the tools
In VS2010 with PPT, when I pinned tabs I got (in effect) two rows of tabs.
I see that no longer works in VS2012 / PPT.
And I wanted (and requested, very nicely) MULTIPLE tab rows.
While I use a portrait mode monitor and have less width to work with (enough for about five file tabs), I'm sure other developers open lots of files and would like to see multiple tab rows, too.
I got a very nice REPLY when I requested this for PPT / 2010, but I'm sad to say now there's only a single row even when pinned.
Please consider supporting multiple tab rows in the tab well on PPT / 2012.
Thanks again for considering this again.
This is still an issue with the latest update.
With the custom document well turned off, pinned tabs are remembered across VS sessions and when going in and out of debugging.
With the custom document well turned on, pinned tabs are NOT remembered. If you start debugging, all pinned tabs are converted to normal tabs. These tabs do not become pinned again when you restart debugging.
Is there any way to hook into the underlying "pinned" status and use that, as it appears to be working as expected?
This happens to me only when "Maintain pin status if document is removed from well" is unchecked in the main VS2012 options (Options -> Environment -> Tabs and Windows). If that's checked, the pin status survives a restart. The issue only happens when Productivity Power Tools 2012 is enabled -- maybe the extension is doing something to tabs at some point upon closing that VS interprets as "removing from well"?
At any rate, it's not ideal, but checking that option fixes the issue for me.
The "maintain pin status" option does seem help across VS sessions, but doesn't help when debugging.
I hope that one of the developers stops by here to have a look at some stage, because I love the custom well but cannot use it in the current state.
This just started recently since the last update (which I installed on 4/23, but I believe is the 4/4 update). Whenever VS opens, the window is maximized. If I try to move the window by mouse, then the window immediately locks up and becomes unresponsive, I have to terminate the process. If I only aero-snap the window using Win+Left/Right, then the window will snap to the sides of the monitor, but as soon as it comes to the point in the rotation where the window is in a 'restored' state, not snapped to any edge of the screen, or maximized, it locks up. I get a generic error in the event log that mentions just that Visual Studio stopped interacting with Windows (how rude! :) ).
I determined the error by disabling all extensions and then moving the window worked again. I then turned on extensions 1 by 1 until it failed, which so happened to be with this extension. I currently have the extension disabled, but I LOVE this extension and use it all the time. Please advise on how I can fix this!
I have already uninstalled the extension and reinstalled it, as well as trying a repair installation on Visual Studio.
At least it is when you both put it next to a commonly used option (Close) and don't ask the user if they're sure they want to close all of their tabs. I don't care if all the work is saved - my flow is gone now because I have to pick through a huge solution and remember what all I was looking at. This is not OK and if some plugin API limitation prevents you from throwing up an "Are you sure you want to do this" dialog, then you need to move that option - possibly below some options that don't actually do anything - just to keep it away from the others.