- #HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS HOW TO#
- #HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS UPDATE#
- #HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS WINDOWS#
msi’ option in the custom build task or manually copy it out to the artifacts directory. Make sure to either select the ‘Create artifact for. To do this in the pipeline add a command line task (Set EnableOutOfProcBuild step in the image above) and use the scripts based on the appropriate VS version. Running the DisableOutOfProcBuild.exe solved the issue. Soon figured out that this was faced by others in the past. HRESULT = ‘8000000A’, when running this build through the pipeline. I ran into the error message An error occurred while validating. Setting up the custom task is straightforward - you can either choose to build just one particular installer-project in the solution or all of them in the solution. Since MSBuild cannot be used to build these projects you need to make sure you have Visual Studio installed on the agent with the Installer Projects extension installed. The Build VS Installer is a custom task that can be used to build your Visual Studio Installer projects (.vdproj files). In your build pipeline definition make sure to select the new custom agent as your default Agent pool. To find the scope ’ Agent Pools (read, manage)’, make sure you click the ‘Show all/less scopes’ link towards the bottom of the page (as shown in the image below) - At times some things just miss your eyes! Rest was pretty straightforward, and you can have the custom build agent set up in minutes. The only tricky thing with setting up the custom agent was step 4 under Prepare Permissions.
#HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS WINDOWS#
I set the custom agent on a Windows machine and have not tried on any of the other variants. Hosted agents do not support this at the moment. The only way I could find to get the Installer Project to run and build out an MSI file was to set up a custom build agent. The Visual Studio Installer Projects require a custom build agent. Once you have the installer project set up locally and have the MSI file generated on building solution, we can set this up in Azure DevOps pipeline and automate it.
#HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS HOW TO#
If you are looking to how to set up the Installer project, this stackoverflow answer shows you exactly how. By adding this setup project to the solution, you can create a setup file that steps through a wizard and installs your application. Microsoft Visual Studio Installer Projects is available as an extension to Visual Studio and provides support for Visual Studio Installer Projects in Visual Studio. Visual Studio Installer Projects (*.VdProj) Net Framework and looking around for installer options I found mainly two approaches discussed below. I wanted the MSI created in the build pipeline, in this case Azure DevOps, and publish the MSI as a build artifact. Recently I was looking into packaging a Windows Service as an MSI installer. Hopefully someone else out there has seen this and has a suggestion. I've spent the entire morning running searches with various keywords but I haven't found any other suggested fixes. The bottom line is that Installer Projects load and run just fine, *except* during when Visual Studio is loading the entire solution.
#HOW TO USE MICROSOFT VISUAL STUDIO 2017 INSTALLER PROJECTS UPDATE#
I've tried running the "gacutil.exe" commands from " Update to 15.8.0 - projects won't load - Developer Community" and I've tried deleting the ".vs" folder in my solution folder. I can then build my solution and use the installer projects to create the installer. If I then rename the two Installer Project subdirectories back to their original names and click on each installer project in Solution Explorer and select "Reload Project" from the pop-up context menu, the projects load without errors. If I rename the two Installer Project subdirectories in my solution folder, I can open the solution without problems aside from the two dialogs that indicate the Installer Projects can't be found. Now when I open my solution file, Visual Studio displays a dialog stating "Preparing Solution" and hangs there until I kill Visual Studio. I've been using the Microsoft Visual Studio Installer Projects extension v0.9.0 without problems with the earlier version of Visual Studio 2017. I have a solution that contains 7 projects, 2 of which are Installer Projects. I recently updated my Visual Studio 2017 installation from v15.9.7 to v15.9.9.