This is indispensable to anyone moving from an older version of Visual Studio who made use of macros. I have also found it can be used to automatically save all files before running an external tool (another very useful option which was left out of more recent versions of Visual Studio). Although I don't require the extra features in the paid version I may have to buy it anyway as it has been such a life saver.
Worked well as expected, and basically allows me to fully transition from VS2010 to VS2013. Pleased about this and bought the pro version as a result. Minor niggles that made this 4 star rather than 5;
Commands should be optionally be referenced by name rather than number, as it makes assigning them to keys a bit easier. e.g. VCMD.MyKickAssMacro rather than VCMD.Command01
A bit more documentation on the compile errors would be useful. Pro version is better than the free version in this regard, as double clicking on the error brings you to the offending line. Doesn't seem to happen in the free version.
All in all, a great solution to a major shortcoming in VS2013
Was able to cut&paste my old macros into it and it worked fine with no issues.
Not sure if this was because I already had a different macro tool installed, but the typical Microsoft MACRO shortcut keys used to launch the RECORD (Ctrl-Shift-R) & RUN (Ctrl-Shift-P) were not mapped to the equivalent actions on this tool. In any case, I had to manually map them.
That was not a biggy, considering how happy I am with the tool!
Thanks for saving us from another MS #$%^ decision...
It says that "Code of an existing Visual Studio macro from previous versions of Visual Studio can be just pasted in the Run subroutine of a new VB command." !!!! COMPLETELY FALSE !!! I tried to import an older macro from VS 2005 and it has TONS OF PROBLEMS because the VB language itself has changed in the mean time and, of course, a lot of the objects are not available any more.
I realize this is mostly Microsoft fault , but I do not tolerate bold statements as the one mentioned before. I lost half a day trying to do this and I still have lots of errors to correct.
I'm using "VisualCommander 2.2 .vsix", Visual Studio Community 2015.
When assigning macros to keys, I see the macro names (and numbers);
however, I don't see the names when adding toolbar items (buttons).
Is this a bug ?
If you are referring to the Friendly command names for keyboard bindings feature of the professional edition, it indeed doesn't apply to adding toolbar items as I haven't found a VS API allowing it.
I am trying to install the latest version of visual commander in vs2013 ultimate with update 4 but get the following:
[Visual Commander] Unhandled exception
System.NullReferenceException: Object reference not set to an instance of an object.
at SergeyVlasov.VisualCommander.VsTextViewCommandFilter.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
Is this a known bug? The OS is Swedish Windows 8.1 x64
I am currently migrating a development system to Visual Studio 2013 Express and your Visual Commander looked perfect for enabling me to continue using my old comment macros. Unfortunately it refuses to install saying I have no compatible products. Do you know if this is a limitation of the Express version (as other people seem to be using it on VS2013) or something you could fix?
Visual Studio 2013 Express doesn't support any extensions, including Visual Commander. You may want to try Visual Studio 2013 Community Edition:
First, thanks for the really useful VS extension.
I am running VS2012 Pro with the latest Commander. I recorded a macro, but when I try to run it, I get COM exception 0x80004005 if I try to run
However, this line works:
as well as these 2 lines:
EnvDTE.TextSelection ts = DTE.ActiveWindow.Selection as EnvDTE.TextSelection;
(DTE.ActiveDocument.Selection as EnvDTE.TextSelection).Text = @"some text";
Is there a way to fix the Edit commands problem?
The problem was in the way I invoked the macro. I tried to run the macro via Run button in Commands window and this is when it failed. After I assigned the macro to a keyboard combination, everything works like a charm! Such a relief... . Having an option to use C# is great.
I am trying to do the same, but in my VS2008 there is a whole tree of macros:
I am interested in the macros from VSEditor but they reference the Utilities and so do not compile when placed in Command.
Is that still possible to import all the old macros in one easy step?
Hello I have a question please.
I'he tried to install Visual Commander v1.6 - March 3, 2014 (limited edition)
in Visual Studio Prpfessional 2012 and Ultimate 2013 Update 2 tryal version.
Both VS in Italian language.
But after installation I can't see the VCMD window like in your home page (http://vlasovstudio.com/visual-commander/).
I need VS english version or can I use VCMD in italian version too?
I've just installed VS Ultimate 2013.2 Italian on a VM and I do see the main VCMD menu after Visual Commander installation.
Is Visual Commander at least visible and enabled in "Estensioni e aggiornamenti" on your machine?
OK, thank you Vlasov.
Seattle Seahawks won the super weed bowl !
After the game, a 30 foot high bonfire was lit
next door to me. Burning couches.
It nearly caught trees on fire.
FireFighters put it out ASAP.
I want -all- file types to open in
the text editor with -nothing-but-
the per glyph font/colors I specify.
For example, I want all digits, everywhere,
to have a certain color/font.
And I want to do this by handling certain events,
in a Visual Studio 2013, "Visual Commander" extension.
Problem is, I don't know what those events are,
or how to handle them.
Can you help me with this, Sergey Vlasov ?
You probably want to create a Visual Studio Editor Classifier. It uses MEF for registration that is not currently supported by Visual Commander.
There is a Visual Studio SDK template for a classifier, if you want to get started writing it yourself, see http://msdn.microsoft.com/en-us/library/vstudio/dd885492.aspx
And there is the open source KeywordClassifier Visual Studio Extension that already allows you to customize which keywords get highlighted, see https://github.com/tomasr/KeywordClassifier
I'm using version 1.2.1 in VS 2013. I added a reference to a dll in the Command editor (References button). I specify the dll in 1 line like:
And it fired an exception. With assembly binding log enabled, it seem to try to find the file within the program files folder:
Program Files\Microsoft Visual Studio 12.0\Common7\IDE\