Feel like a master.
Why vsCommandEvent ?
vsCommandEvent was based on vsSolutionBuildEvent engine and still continues mission to provide flexible actions for your environment!
Means advanced handler of the most events but unlike the first it specialized for advanced work with the Visual Studio commands and its data as manager of this on the fly.
The dev environment of any users may be flexibly changed as you need in a few steps.
You can even override the 'Exit' (including [X] and Alt + F4 hotkey) for Visual Studio IDE on the fly 🔧.
A new look at old things
In comparison with vsSolutionBuildEvent, Why not look at some similar solutions from there.
It cannot be same as for vsSolutionBuildEvent because it works on another technologies. But let's try to look closer. Can we achieve the same result via vsCommandEvent manager?
Solution-wide Build Events
vsCommandEvent initially may work with commands from VS. Thus, you can catch commands when starting the any Build operations still for the entire solution or individually for each project separately.
Automatic Version Numbering
Still available versioning as you prefer. Moreover, with an vsCommandEvent you can handle versioning for most operations of Visual Studio. Just try as you need.
Stop build on first error
Disturbs [Warnings] and [Errors] ?! no problem, manage it:
vsCommandEvent provides most the action types from vsSolutionBuildEvent engine:
Supports advanced MSBuild & SBE-Scripts engine for powerful usage. And lot of other features for the convenience of your work with the build, tests, versioning, IO operations, and so on. See the documentation.
A few modes for you:
You can also choose this as an preferred action type.
Through E-MSBuild engine.
https://github.com/3F/SobaScript -- Extensible Modular Scripting Programming Language.
Use our available components or extend everything by creating new.
Feel free to improve any our pages. Click [Edit] button or Start new page here.
Questions / Bugs / Suggestions / Source Code
👉 Screenshots: [ . . . ]