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. 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. 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.
0 kommentar(er)
