Installation
Visual Studio
You need VSPackage (.vsix) file. Find it from the Download page. Or see latest binaries from GitHub Releases Page
Complete Installation Guide
SDK10 / SDK15 versions
- Starting from VS2019 you need use only SDK15 packages.
- VS2017: SDK10 or SDK15 (recommended)
- VS2010, VS2012, VS2013, VS2015: SDK10
- CI /Build Servers, msbuild tools: SDK10 or SDK15
- Devenv Command Line version: SDK10
- API: SDK10 or SDK15
Upgrading to Visual Studio 2019
-
[VS2019]
Build can be started before activation of our plugin inside VS IDE.This is a feature of the modern VS platform with lazy loading of all plugins. But you can still affect for priority activation:
Solution: Just attach once our [status panel] from
View
-Other Windows
and this will always activate our plugin before start. -
Deactivated/Inactive [Status Panel] from
View
-Other Windows
.Incorrect identifier in previous version produces wrong tool.
Solution: Just close this panel. Then, open it again fromView
-Other Windows
.
How to build vsSolutionBuildEvent
We finally migrated to GitHub: https://github.com/3F/vsSolutionBuildEvent
For build you need also vsSolutionBuildEvent v0.12.8+
- All dependencies is managed by GetNuTool & NuGet and will be received automatically.
The build is possible for all VS versions starting from VS2010! Via MSBuild tools and Visual Studio.
Debug at runtime via Visual Studio IDE
vsSolutionBuildEvent project
Find the vsSolutionBuildEvent project in solution:
- Set as StartUp project
- Open
Properties
>Debug
:- Start Action - set as
Start External program
- Then, select your devenv.exe, eg.: C:\Program Files (x86)\Microsoft Visual Studio 16.0\Common7\IDE\devenv.exe
- In Start Options > Command line arguments: '/rootsuffix Exp' (without quotes)
- Start Action - set as
CI.MSBuild project
Find the CI.MSBuild project in solution:
- Properties -> Debug:
- Start Action - set as
Start External program
- Add the full path to msbuild.exe, for example: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe
- Optional, add path to vsSolutionBuildEvent sources in
Working Directory
field, for example: D:\projects\vsSolutionBuildEvent\ - In Start Options > Command line arguments, for example:
- Start Action - set as
"<path_to_SolutionFile_for_debugging>.sln" /nologo /noconsolelogger
/l:"CI.MSBuild\bin\<Current_Configuration_Name>\CI.MSBuild.dll";lib=vsSolutionBuildEvent\bin\<Current_Configuration_Name>\ /verbosity:Diagnostic /t:Rebuild /p:Configuration=<Configuration>;Platform=<Platform>
Devenv project
Find the Devenv project in solution:
- Properties -> Debug:
- Start Action - set as
Start External program
- Also select your devenv.exe, eg.: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
- In Start Options > Command line arguments: '/resetaddin Devenv.Connect' (without quotes)
- Enable Debuggers - enable the
Enable the Visual Studio hosting process
- Start Action - set as
- Command line arguments, for example:
"D:\app\App1.sln" /Rebuild
- Also add 'Devenv.AddIn' into your '%HOMEPATH%\Documents\Visual Studio 2013\Addins' with full path to assembly, for example: '
D:/full_path_to/Devenv.dll '
- Also add 'Devenv.AddIn' into your '%HOMEPATH%\Documents\Visual Studio 2013\Addins' with full path to assembly, for example: '
Build via MSBuild tools (Microsoft Build Tools)
- Clone repository. Then, just command build:
.\build DBG
We're also using the following build helpers:
What's next ?
- Create New component
- Improve all what you want…
We are waiting for your awesome contributions! via GitHub