Visual Commander Professional is a commercial edition of Visual Commander. The Professional Edition supports up to 99 commands and 50 extensions (the free edition supports only 10 commands and 5 extensions).
Additionally the Professional Edition adds:
[Doesn't work in VS 2022 v17.5+.]
The Professional Edition integrates the Visual Studio text editor and adds IntelliSense and syntax highlighting for C#/VB code editing:
With the Professional Edition in Visual Studio 2017 you can select C# v6.0 to compile snippets (the free edition supports only C#/VB v4.0) and use features like string interpolation in your code:
In Visual Studio 2017 you can use C# v7 features like local functions:
In Visual Studio 2019 you can use C# v8 features like nullable reference types:
In Visual Studio 2019 and Visual Studio 2022 you can use C# v9 features like records:
With the Professional Edition you can create common code modules and reuse them from commands and extensions:
The Professional Edition allows you to reorder commands, extensions and common code modules with the mouse in the corresponding window and sort them by name with a single click on the Sort button:
Commands in the VCmd menu are then displayed in your custom order:
With the Professional Edition you can double-click on a compiler error in the Compilation status box and navigate directly to the relevant code (line and column of the error):
In the Professional Edition command names for keyboard bindings include your custom command names with the VCmd.CCommand prefix:
The Professional Edition allows you to debug command execution with the Visual Studio debugger.
1. Check the Include debug information option and add the System.Diagnostics.Debugger.Launch() call where you want to start command debugging:
2. Run the command as usual and select a Visual Studio debugger when the Visual Studio Just-In-Time Debugger dialog opens:
3. Now you can step through your code, inspect variables and add standard Visual Studio breakpoints:
If a debugger is already attached to your Visual Studio instance where the command is executing, you can use Debugger.Break() instead of Debugger.Launch() to break execution from code. Or you can call the following universal method:
static private void BP() { if (System.Diagnostics.Debugger.IsAttached) System.Diagnostics.Debugger.Break(); else System.Diagnostics.Debugger.Launch(); }
The personal license allows you to use Visual Commander Professional on any number of computers or electronic devices, but you may not permit other individuals to use your license. Purchase of the personal license includes 1 year of software updates and technical support.
You will receive your registration code via e-mail after your order completes. We offer an unconditional 30 day money back guarantee. If for some reason you are not satisfied with Visual Commander Professional, you can return it for a full refund.
Copyright 2008 - 2025 Vlasov Studio (Best in class Visual Studio extensions and tools)