Visual Commander is a free extension for Visual Studio 2010+ allowing you to automate repetitive tasks in the IDE. You can reuse existing Visual Studio macros from previous versions of the IDE and create new commands and extensions in C# or VB with full access to the Visual Studio automation model and .NET framework.
Visual Commander v1.2 adds the ability to record your editing operations in the Visual Studio code editor and replay them multiple times. Just select the Record Macro command, perform editing on a sample text block and select the Stop Macro Recording command (or press the same keyboard shortcut you used to start recording, typically Ctrl+Shift+R). Now you can replay the macro with the Run Macro command or a keyboard shortcut (typically Ctrl+Shift+P).
A macro can be recorded in VB or C# and you can edit the recorded commands (for example, to add repetition or conditional logic):

Sample macro code in VB
Having access to the macro code, you can copy it to a new Visual Commander command if you plan to use it regularly later. Currently only editing operations are recorded (typed characters, cursor movements and copy/paste/delete commands). I’m collecting feedback on what additional operations should be automatically recorded. Many use Visual Studio find functionality for editing, it is not currently recorded, but as a simple workaround you can manually add the call to the DTE.Find.Execute() method when needed.
I am using VS2010 and try to use you macro recorder with it.
I can record and edit Macros with your tool, but as soon as I try to RUN a macro, I get an error dialog:
Visual Commander, Unhandled Exception,
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderException property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at SergeyVlasov.VisualCommander.Activator.FindType(Assembly a, Type type)
.
.
.
What can I do to use your tool without this error?
Thanks
Andreas
Andreas,
Does this error occur if you run an empty macro?
Andreas,
This exception happens when several different Visual Studio versions were installed on the same machine. I’ve fixed it in v1.3.