Make VS.NET / 2005 thru 2017 / Delphi Prism Action
The Make VS.NET / Make VS 2005 thru 2017 / Make Delphi Prism custom actions create a step for building Microsoft Visual Studio .NET 2002 thru 2017 and Embarcadero/CodeGear Delphi Prism projects and solutions to set or increment version and/or property information in an assembly attribute or resource file.
This action adds functionality missing from Microsoft's command-line tools: It supports setting or single-incrementing project, assembly attribute, and/or resource versions and properties, setting the output file path and attributes, building multiple or all solution configurations, upgrading solutions, setting the project's DLL base address, and more.
This action wraps the devenv.com/msbuild.exe/vcbuild.exe command-line compiler, modifying project settings if specified, updating resource and assembly info files as necessary, and then invoking devenv.com or msbuild.exe to perform the build. See the VStudio.bld sample for sample usage.
Note: If Visual Build doesn't detect that this product is installed when first run, this action will not be displayed (existing steps will still be displayed in the Step panes and will build normally). To show all hidden actions, right-click in the Actions pane and choose Show Hidden.
This action supports solutions and individual VC++.NET (managed, unmanaged, and Intel C++ Compiler projects), C#, VB.NET, LightSwitch, J# .NET, Delphi Prism (.oxygene), Web Deployment (.wdproj), Reporting Services (.rptproj), Analysis Services (.dwproj), Integration Services (.dtproj), and WiX projects (.wixproj), and all Windows, web, and Smart Device (.NET Compact Framework) project types (other project types in a solution will be built, but the added features will not be performed for them), and also individual RC and assembly attribute files. It has been tested with Visual Studio .NET 2002 thru 2017 and Delphi Prism and may also work with other versions.
1) During installation of the Intel compilers, the Visual Studio Integration option is included and all update environment variable options are checked.
2) The projects are converted to use the Intel C++ Project System (in the VS IDE).
3) The project or solution is built with devenv (specified in the Override field of the Options tab).
|•||When using this action to build projects or solutions for Visual Studio 2005 or later, MSBuild will be used by default. Only the .NET Framework must be installed; Visual Studio does not need to be installed on the build box. This behavior can be overridden by specifying the full path+filename of the compiler executable on the Options tab. When building projects with devenv.com or VCBuild, Visual Studio or VCBuild must also be installed on the build box.|
|•||When building Visual Studio 2002 or 2003 projects or solutions, the appropriate version of Visual Studio must be installed on the build box.|
|•||MSBuild does not support building of setup and deployment projects (or solutions containing them). Enter devenv in the Override field on the Options tab to build projects or solutions containing Visual Studio 2005+ setup projects.|
|•||This action can also be used to build solutions and projects with Xoreax IncrediBuild (v2.0 and later). On the Options tab, set the Override default DEVENV location (or define and use a global macro) to the full path to BuildConsole.exe (usually C:\Program Files\Xoreax\IncrediBuild\BuildConsole.exe), and enter any IncrediBuild-specific switches in the Additional command-line options field.|
|•||See the VStudio.bld sample for a project utilizing this action.|