I would like to be able to use Package-Web in such a way that if I use the new Build (recently called "vNext") workflows in Visual Studio Online, I can specify an argument to the publish process so that the transform is applied during the publishing process. For example:
Azure Subscription: My Subscription
Web Site Name: My Website
Web Site Location: East US
Slot: Staging
Package: BuildOutput\_PublishedWebsites\MyWebsite.zip
Additional Arguments: ???
I'm not overly familiar with the MSDeploy process, but from looking at the interactive PowerShell script it appears that the site is extracted first to apply the transform, and then it is deployed. This wouldn't seem to fit with the way that VS Online deploys packages to Azure Web Apps using the "Azure Web Site Deployment" task.
Either can package-web be updated to support this scenario, or can the appropriate documentation/guidance be provided to allow people to easily use package-web in this way if it is already supported.
For example, I would expect in the easy case that for the Additional Arguments option in the Build Definition I could specify the name of the transform to be applied before publishing (e.g. Staging).
I would like to be able to use Package-Web in such a way that if I use the new Build (recently called "vNext") workflows in Visual Studio Online, I can specify an argument to the publish process so that the transform is applied during the publishing process. For example:
I'm not overly familiar with the MSDeploy process, but from looking at the interactive PowerShell script it appears that the site is extracted first to apply the transform, and then it is deployed. This wouldn't seem to fit with the way that VS Online deploys packages to Azure Web Apps using the "Azure Web Site Deployment" task.
Either can package-web be updated to support this scenario, or can the appropriate documentation/guidance be provided to allow people to easily use package-web in this way if it is already supported.
For example, I would expect in the easy case that for the Additional Arguments option in the Build Definition I could specify the name of the transform to be applied before publishing (e.g.
Staging).