So I've got my deploy working on a build and I've set up my build to create a deployment package and execute the package on the target server. Great so far. Now however the application is expanding and I need to have different configurations per machine (account names and such like),
Can I specify what the file name of "setParameters.xml" for example to "Server1.SetParameters.xml" or similar ?
I've got it copying the files over the SetParameters.xml before each deploy for now but is seems in-elegant and should a file get locked for what ever the reason it would deploy the wrong settings to the wrong server.
/p:DeployOnBuild=trueand/p:DeployTarget=PackageI'm then executing the package in theAfterDropBuildtarget using exec and a file path like_PublishedWebsites\Website_Package\Website.deploy.cmd /Y /M:Server1 /U:User /P:PasswordWhich I think is the second option but if using msdeploy directly I'm happy to switch.Website.deploy.cmd /Y /M:Server1 /U:User /P:Pass -setParamFile:Server1.SetParameters.xml