Fork me on GitHub
Developer Zone

Developer Zone How to build New Component for SBE-Scripts core IPM analyzer Dom & Code Completion Scheme of vsCommandEvent Ask a question ...

How to build

How to build vsCommandEvent Branches status: Source Code Nightly builds Snapshots Currently it is similar for vsSolutionBuildEvent - see documentation here What's next ? Create New component Improve all what you want… Is also ready for collaboration ? use pull request features or send directly as .patch file. For complex logic(as for our lexers, analyzers etc.) please also provide a correct new unit-tests. ...

Developer zone. SBE-Scripts

Developer zone. SBE-Scripts Dom & Code Completion IPM analyzer for SBE-Scripts core ...

Available Events

...

Examples

Complete Solutions Overriding of commands Automatic Versioning Stop build on first error MSBuild engine The documentation here Some features Math operations Date & Time .vsce File format Solution-wide Build Events Confirmation dialog Exclude projects from build Work with external utilities Increment & Decrement Numbers [custom counters] Operations with strings Remote servers Processing modes Processing modes Scheme of vsCommandEvent Read here For developers See Developer Zone - How to build plugin; How to create component for current platform; etc. Your experience Feel free to improve any our pages. Click [Edit] button below or Start n ...

Stop build on first error

Stop build on first error The vsCommandEvent also contains this feature and you should use this documentation, however with next notice: Instead of "Errors-Build" event, you should configure the Output window tab: variant Guid Item Condition Type № 1 {1BD8A850-02D1-11d1-BEE7-00A0C913D1F8}   \s+error\s+([^:]+): Regexp № 2   Build \s+error\s+([^:]+): Regexp if you need control of errors and warnings, use for example: Condition Type \s+(?:error|warning)\s+([^:]+): Regexp How to get t ...

Overriding of commands

Overriding of commands The all environment of any users may be flexibly changed as you want for different cases… This possible because the vsCommandEvent may override a lot of commands from Visual Studio, and due to the fact that it is based on vsSolutionBuildEvent engine it also provides a lot of flexible actions as you need… How to Let's consider a simple example. How about to override the 'Exit' (including Alt + F4 hotkey) form Visual Studio IDE ? And how about to set actions below instead of original: Copy all data from VS Output Window. Then create new text file, open and activate it. Finally - Paste the log data from VS Output Window. And supress termination of Vis ...

Automatic Versioning

Automatic Versioning Yes, it's also possible for vsCommandEvent, it means - why not… How to The vsCommandEvent may work with commands from VS, so you can catch command when started the Build or Rebuild, Clean etc. for all solution as for all projects at once or similar…1 Moreover, you can handle of versioning for most operations of Visual Studio. Simply try as you need. In general you should configure commands, and use this (for example) the documentation - Automatic Version Numbering And also here you will see commands for Build, Rebuild, Clean operations for solution. References Examples & Features Processing modes SBE-Scripts Visual Studio Gallery page ...

Features

Some features Confirmation dialog / Prompt window Custom counters Date & Time Exclude projects from build Work with external utilities Math operations ...

Solution-wide Build Events

Solution-wide Build Events Yes, it's also possible for vsCommandEvent, it means - why not… How to The vsCommandEvent may work with commands from VS, so you can catch command when started the Build or Rebuild, Clean etc. for all solution as for all projects at once or similar… However, it cannot be same for vsSolutionBuildEvent, because he work on another technologies. Here, you will know more about how to work with commands, and for this case you should configure EnvDTE tab, for example: Description Guid Id in out Started - Build Solution {5EFC7975-14BC-11CF-9B2B-00AA00573819} 882     S ...

vsCommandEvent/vsCE (.vsce) File

.vsce The vsCommandEvent also uses the JSON format (text-based language-independent data interchange format) Where it placed ? It should be 2 places below: Common .vsce The common settings for all your Visual Studio should stored in: %HOMEPATH%\Documents\ -> Visual Studio <num>\vsCommandEvent directory. Where <num> is version of used Visual Studio. For example: C:\Users\<user>\Documents\Visual Studio 2013\vsCommandEvent\.vsce .vsce for Solution Optional, your settings may stored with specific solution. For this case, all configuration can be shared for other users. You can manage of this in Settings - Configuration: Enable Use Solution context if need stori ...

Installation

Installation and removal VSPackage The main plugin. Contains logic for work with events of Visual Studio and core of different actions for anything. To install: Get latest build vsCommandEvent_v1.2.0.11076_a7bae2f_net40.vsix and restart VS IDE. That's all. If you received file with different extension: simply change on .vsix or install manually with command: VSIXInstaller.exe <downloaded_file> To remove: VS IDE - Tools - Extension and Updates ...: Uninstall or Disable If you need manually: VSIXInstaller.exe /uninstall:DA5CEB32-1E09-44A5-A6AA-71D3149A53B7 ...

How to correctly report

How to correctly report Next information will be helpful: Your version and edition of Visual Studio. For example: VS2013 Professional Version 12.0.30501.00 Update 2 The Version of vsCommandEvent where you see bug or some problem. The other version where problem not exists if you know. Logs: To enable 'Debug Mode' and reproduce problem again. Any dump of crashes - minidumps or simply like this And most importantly: Steps of how to reproduce your problem. + additional information if you think that's necessary to report: projects type (e.g. C#, C++, ..), data, environments, full moon tonight, and another … Remeber: We support the all ve ...

Processing modes

Processing modes Currently the most of processing modes are similar to original from vsSolutionBuildEvent. The documentation here The differences C# Mode EnvCommand Mode Operation Mode ...

C# Mode

C# Mode This action type for work with C# compiler - feel free with all events & actions. The vsCommandEvent has some differences from original engine Default Entry point using ICommand = net.r_eg.vsCE.Actions.ICommand; using ISolutionEvent = net.r_eg.vsCE.Events.ISolutionEvent; namespace vsCommandEvent { public class CSharpMode { public static int Init(ICommand cmd, ISolutionEvent evt) { return 0; } } } ...

EnvCommand Mode

EnvCommand Mode This action type for raising of different commands for EnvDTE (Assembly-wrapped COM library containing the objects and members for Visual Studio core automation. http://msdn.microsoft.com/en-us/library/EnvDTE.aspx) How to use In general, for work with EnvDTE commands you can use our sniffer tool: Settings - Tools - EnvDTE Sniffer The Enum column should describe about place for this command, for example: {1496A755-94DE-11D0-8C3F-00C04FC2AAE2} 1628 Microsoft.VisualStudio.VSConstants+VSStd2KCmdID.OutputPaneComboList Where: Microsoft.VisualStudio.VSConstants+VSStd2KCmdID.OutputPaneComboList tells us about operation - OutputPaneComboList For all this, firstly, yo ...

Operation Mode

Operation Mode The vsCommandEvent contains same mode with differences below. After selecting of this mode, you should use list of commands in the corresponding columns: i.e. the vsSBE users should write commands 'as is' instead of Build.SolutionConfigurations(Debug) and similar… ...

Create new page

Create The our Wiki based on GitHub services, so simply click here Then create or select any subpath from _doc/ directory and name your file as you want with .md extension. Just add the following header: --- layout: doc title: <Your title> permalink: /doc/<path>/ --- Where <path> should be to .md file without extension. For example, set /doc/My-Page/ if you will add the My Page.md in root _doc directory. Now you're ready to create your awesome page below from this header. Use markdown syntax or see existing pages. Markdown syntax Test on this page https://guides.github.com/features/mastering-markdown/ Highlighting Use thi ...

Scheme of vsCommandEvent

Scheme of vsCommandEvent The vsCommandEvent has more lightweight structure instead of vsSolutionBuildEvent Structure Information for this section temporary is not available. To fix it, click - Edit Model of events The vsCommandEvent works on the similar Event-Actions model, i.e.: There is an configured event from Visual Studio. And exists some actions, that to be executed… Basic work is a: Configure the event. Create and configure any actions for this. Enjoy. References vsSolutionBuildEvent Examples ...

Scripts & Commands

Scripts & Commands The vsCommandEvent provides advanced actions for all events. User scripts and commands as part of this: SBE-Scripts MSBuild Processing modes - Available modes with C# & MSBuild Targets, etc. References Examples & Features ...

MSBuild

Special MSBuild Properties List of special properties that available as MSBuild Properties. name description sample of value availability vsCommandEvent The version of the vsCommandEvent engine. 1.1.0.634 v1.1+ vsCE_LibPath Full path to library. C:\Users\reg\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\ubnc5xvo.xia\ v1.2+ vsCE_CommonPath Common path of library. C:\Users\reg\Documents\Visual Studio 2015\vsCommandEvent\ v1.2+ vsCE_WorkPath Working path for library. D:\prg\projects\Conari\Conari\ v1.2+ ...

SBE-Scripts

The vsCommandEvent contains same engine, however also have differences in a few components. Arguments Information for this section temporary is not available. To fix it, click - Edit Object type The object type is new type for work with complex mixed data. It implemented special for vsCommandEvent. Value can be from all available scalar types + complex, like this: {} {"str", true} {"str", {1, 'y', {-12.457f}}, true} etc. List of avaialble components Currently the most of the components are similar to original from vsSolutionBuildEvent The documentation here The differences Please see a list of changes for chec ...

SBE-Scripts. Available Components

SBE-Scripts. Available Components DTEComponent For work with EnvDTE. InternalComponent All internal operations with vsCE. OWPComponent Works with OWP and similar operations. ...

DTEComponent

DTEComponent For work with EnvDTE (Assembly-wrapped COM library containing the objects and members for Visual Studio core automation. http://msdn.microsoft.com/en-us/library/EnvDTE.aspx) This component has some differences from original vsSolutionBuildEvent Method raise Raise Command ID for EnvDTE. Syntax: void raise(string guid, integer id, object customIn, object customOut) Arguments: guid - Scope by Guid. id - The command ID. customIn - Mixed input parameters. customOut - Mixed output parameters. Note: customIn & customOut may contain mixed data, inc. complex object as: {}, {"str", true}, {"str", {1, 2}, true}, etc. Sample: #[DTE raise("{5EFC7975-14BC-11CF- ...

InternalComponent

InternalComponent All internal operations with vsCommandEvent. This component has some differences from original vsSolutionBuildEvent Entry point for component The vsCommandEvent requires the next name for all internal operations: vsCE or alias Core Samples: #[vsCE ...] #[Core ...] ...

OWPComponent

OWPComponent For work with OWP (Output Window Pane) and similar operations. This component has some differences from original vsSolutionBuildEvent log Provides data from events of logging. Has been disabled for vsCommandEvent version out For streaming of getting the mixed data from selected pane. Syntax: #[OWP out(string ident [, boolean isGuid])] Arguments: ident - Name of pane. isGuid - Optional flag to use Guid as identifier if true, otherwise as name of item. MSDN. Guids of Output Pane BuildOrder: 2032b126-7c8d-48ad-8026-0e0348004fc0 BuildOutput: 1BD8A850-02D1-11d1-BEE7-00A0C913D1F8 DebugOutput: FC076020-078A-11D1-A7DF-00A0C9110051 … ...