Visual Commander Professional v1.3 Introduces 99 Commands, 50 Extensions and C# Syntax Highlighting
Visual Commander Professional v1.3 has been released with the ability to create 99 commands and 50 extensions either by pressing the Add button in the Commands window or by import. It introduces syntax highlightingand also integrates Visual Studio text editor to enable developers to edit code and added recording for Edit.FindNextSelected, Edit.FindPreviousSelected, Edit.FindNext and Edit.FindPrevious commands.
Visual Commander v1.3 provides an ability to select default language for new commands and extensions by selecting the macro language. It also provides fixes for ReflectionTypeLoadException, which occurs when multiple versions of Visual Studio are installed on the same machine in addition to a fix for FileNotFoundException that throws when custom assemblies are referenced with the full path. The recent release includes improved storage processing to preserver CR in code and several enhancements in exception handling.
The extension enables developers to automate repetitive tasks in Visual Studio 2013/2012/2010 either by creating new commands and extensions in C#, VB or by reusing existing Visual Studio macros from previous versions. It also provides an ability to record and playback keyboard commands for the Visual Studio text editor.
With the help of Visual Commander, Record Macro (Ctrl+Shift+R) and Run Macro (Ctrl+Shift+P) commands can be reassigned by manually assigning them in Visual Studio keyboard options for the VCmd.RecordMacro and VCmd.RunMacro commands. Moreover, the extension stores all the settings including commands, extensions and the temporary macro in "%APPDATA%\Sergey Vlasov\Visual Commander\1.0\snippets.vcmd".
"There is no API for Visual Commander at the moment. You can assign shortcuts to the commands and add them to the toolbar using standard Visual Studio interface," said Sergey Vlasov, Lead Developer, Visual Commander.
InfoQ had a chat with Sergey to know more about his Visual Studio extension.
InfoQ - Can you share with us the real purpose behing the creation of Visual Commander?
The main goal for Visual Commander was to give developers the ability to run existing macro commands in Visual Studio 2012/2013. Visual Studio supported macro commands since Visual Studio 6, lots of custom commands were created to improve productivity and removal of this feature in Visual Studio 2012 left many developers empty handed. Also no other 3rd party tool have this functionality at this moment.
InfoQ - Does Visual Commander improve developer productivity?
Absolutely. For common tasks you can create a command sequence to edit code, change Visual Studio options or modify your solution and then invoke it with a single mouse click or a keyboard shortcut.
InfoQ - Can you share any case study where the product has been tested successfully?
Jeff Relf posted his experience using Visual Commander Professional to the "Bring back Macros" thread on VS uservoice. The Visual Commander page on Visual Studio Gallery lists 3 reviews and Q&A.
InfoQ - Can you disclose the future roadmap of Visual Commander?
I plan to improve Visual Commander integration with Visual Studio and make it easier to use:
- Add the ability to reorder and sort Visual Commander commands in the VCmd menu.
- Add custom command names for keyboard binding to Visual Studio keyboard options.
- Add explicit menu command to save recorder macro as a command.
- I'd like to find a way to enable intellisense for command editing, but currently hitting limitations of Visual Studio extensibility.
Mike Amundsen May 29, 2015
Ben Linders May 28, 2015