Visual Commander is a great product! I totally recommend getting it if you have been using macros for a long time in Visual Studio and still need to use them. I use macros all the time in my work and because Microsoft stopped supporting the feature in 2012, I was hesitant to upgrade to any future revisions of Visual Studio. Now that Visual Commander is available, I can upgrade without losing my macros!!
Granted, there is somewhat of a "transition process" to get your old macros into Visual Commander, but this is easily overcome and Sergey Vlasov responds very quickly to any questions you might have and will get you going promptly.
I use Visual Studio 2010 Ultimate, and for years I have been manually typing date time flags at the end of lines that I insert or modify. One day I did a search for some kind of macro or other way to do this and, like the Fairy Godmother who emerged from the Grandfather clock, Visual Commander was revealed. Now all I have to do is one keystroke to get my date time flag. I look forward to writing more macros with the paid for version of Visual Commander which I purchased in sheer gratitude. Thank you, Sergey.
(CTRL)(SHIFT)R is preprogrammed to macro recording in the Visual Commander package, but this key combination is usually already assigned to default Visual Studio commands and thus is not activated by Visual Studio shell.
Record a macro with Visual Commander, then assign it to a keyboard shortcut using Tools...Options...Environment...Keyboard. Wonderful! My only criticism is that the command name I entered didn't show up in Tools...Options, so I had to know that it was "Command01".
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 not sure is this a problem with Visual Commander or just with ASP.NET 5.
But a call to typeService.GetTypeResolutionService(hier).GetType(name, true) throws a TypeLoadException exception complaining about not to able resolve "name". The macro works flawlessly with all other configuration.
Visual Commander is just what I need to flag new statements in my code with a date time stamp. I called my command DateTimeStamp and use it after clicking on the end of the line of code that I wish to flag with, e.g., "....;//// 4/9/2016 8:03 AM". All works well using the VCmd menu but not from a keyboard shortcut (Cntrl-T) that I added. The displayed name is "DateTimeStamp Cntrl+T" but when I use Cntrl+T it it moves the final semicolon one place to the left instead of writing out the date and time!
What could I doing wrong?
By default Ctrl+T in Visual Studio is assigned to the Edit.CharTranspose command in the Text Editor context and it looks like it is invoked when you press Ctrl+T.
Please, select "Use shortcut in:" Text Editor when you assign Ctrl+T to the DateTimeStamp command in keyboard options.
I have been using Visual Commander in VS2013 community edition for a while and now find it invaluable. I have recently started using Atmel Studio 7 for AVR development. This is based on VS2015 (as fas as I know). Do you know if it is possible to make Visual Commander work with it? The Visual Commander install doesn't list Atmel Studio when run.
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: