Get latest binaries from GitHub Releases

Build from source

We finally migrated to GitHub: https://github.com/3F/vsSolutionBuildEvent

Download Source Code as .zip or command:

git clone https://github.com/3F/vssolutionbuildevent.git vssolutionbuildevent
cd vssolutionbuildevent

Build SDK10, SDK15, SDK17 using REL configuration

build REL 10,15,17

See CI builds

What's next ?

vsSolutionBuildEvent is waiting for your awesome contributions!

See Developer Zone

Installation

Visual Studio

You need VSPackage (.vsix) file. Read the installation guide here

SDK10 / SDK15 / SDK17 versions

Starting from VS2022 you need SDK17 packages.

  • Visual Studio 2022+: SDK17
  • Visual Studio 2019, 2017: SDK10 or SDK15 (recommended)
  • Visual Studio 2017, 2015, 2013, 2012, 2010: SDK10
  • CI /Build Servers, msbuild tools: SDK10 (recommended) or SDK15 or SDK17
  • Devenv Command Line version: SDK10
  • API: SDK10 or SDK15 or SDK17

Upgrading to Visual Studio 2019

Known problems

  • [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 from View - Other Windows.

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)

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:
"<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
  • 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'