I cannot live without the output window highlighting, debug as, and solutions badges. The solution badges feature alone makes this worthwhile - I often have a half dozen or more instance of Visual Studio open and being able to identify which is which is a life-saver.
I have just got a message that says this version of VSCommander is no longer compatible with Visual Studio as of 20/09/2014 00:00:00 and suggests I get an update. The version installed is the latest. I uninstalled and reinstalled and get the same message.
Same here. Looks like the developer forgot to somehow update either the extension expiration date or the website about this change. The website looks outdated though (not even linking to VS2013 extension on main page).
Since I upgraded to VS2013 Update 3, the Git branch name is no longer displayed:
- in the main window title
- in the solution explorer window title
However I can still see it in the taskbar jump list and Windows task switcher (Alt-Tab).
For some reason, it still works for SVN (using AnkhSVN, if it matters); the problem only occurs with Git (haven't tried Mercurial and TFS).
I recently was told about this extension and wanted to try it out. I saw the inbuilt stack overflow search and jumped for joy, until I found that:
a) it doesn't work well with the dark theme enabled i.e. can't read links as they are too dark etc.
b) there doesn't seem to be anyway, that I've found yet, to change the colours for this panel.
So I was wondering if there is a way to change the colours here so that I can read the results?
Hello, if I purchase a license for VSCommands Pro 11 to use in Visual Studio 2013, may I also use the license for VSCommands Pro 10 for Visual Studio 2010? At work we're still on 2010, but will be moving to 2013 (or newer) in the near future. I was hoping to avoid having to purchase 2 licenses (one for each version if one will work with both).
From what i could read on their website, you'll have to buy a license for each VS version you use....
So if you're planning to change you VS version in a near future i would recommand to wait before purchasing the license.
In IDE Ehancement > Keyboard, i checked "allow Keyboard enhancements" and "Change [Windows Key + arrow] Behaviour"
The problem now is that Aero snap still moves the VS Window all around my desktop when usgin the "Windows + arrow" combination.
For this option to work correctly i have to also check the "Disable Aero Snap" option too.
Is that a bug ?
If not, you should present "Change [Windows Key + arrow] Behaviour" as a functionality of the "Disable Aero snap" feature, because the way it is now can be confusive.
Thanks for the answers
Just an FYI, if one sets the Code Block End Tagger (which BTW is awesome) to navigate on double-click and also has Syntactic Line Compression in Microsoft's Productivity Power Pack 2013 enabled (which it is by default), the double-click is NOT navigating. I disabled Syntactic Line Compression and it works now. Perhaps there is some workaround from your end to enable compatibility between the two, but for the moment being able to navigate is more important to me than the line compression afforded by MS's extension.