We have a package that deploys as a window service. However, the way this has been developed the dev’s want to deploy the executable six times. So a single nuget package that will result in six distinct service executables/processes on the target. They assure many any change to the compiled code would require a redeployment of all 6 distinct executables.
I know I could solve this by creating 6 projects using the same nuget package and a slightly different target location on the target box but I’d prefer to have a single project if possible? Is this doable?
Thanks for getting in touch! You should not have any trouble creating a single project with 6 package steps. If you require a unique installation directory for each package, you can use the Custom Installation Directory variable.
Create a project variable named CustomInstallDirectory, then you can add as many values for this variable as you need directories. Each individual value can then be scoped to a step in your project.
