(Yes, I know the forum is for the msdeploy technology itself - but there doesn't appear to be a forum for the Web Publishing Pipeline)
I'm trying to use the new publish profile support to create a continuous delivery "deployment pipeline", whereby a package/zip is made in the first "stage" and the same package is deployed to various environments using different configurations in later, manually triggered, stages.
What I'd like to do is define my publishing profile in a pubxml file (since that appears to be "The Preferred Way™" moving forward) and publish an _existing_ package (msdeploy archive) using MSBuild rather than MSDeploy (since the latter doesn't support the pubxml wrapper).
Unfortunately, I can't seem to find what tasks/properties are involved to cause this to happen. Can anyone point me in the right direction?
↧