Le déploiement d'un package existant à l'aide de profils de publication

Mise à JOUR 2014-01-28

Garder mon script personnalisé à jour avec le changement de version de VS /Azure SDK a fini par être trop de travail, donc en fait, j'ai été rétrocédés à l'aide de l'généré deploy.cmd script, avec une petite différence:

J'ai commencé à quitter tous mes valeurs de paramètre de la ProfileName.pubxml fichier et au lieu de les mettre dans un ProfileName.paramters.xml (exemple généré dans .SetParameters.xml avec forfait, docs ici). Ces sera automatiquement repris par Visual Studio /MSBuild par la convention et je peux les utiliser lors de l'exécution en passant par -setParamFile:path\to\ProfileName.parameters.xml lors de l'appel de deploy.cmd

Mise à JOUR - UNE nouvelle version de ce script est actuellement maintenu (et documenté) sur GitHub - https://github.com/richardszalay/msdeploy-package-publish

Après beaucoup de creuser, j'ai trouvé que plusieurs des problèmes dans Microsoft.Web.La publication.cibles (v10.5) ce qui empêche ce travail. Pour résoudre ces problèmes, j'ai créé le script MSBuild qui peut être placé dans le même répertoire que l'Application Web csproj. J'ai ajouté des commentaires liés à des correctifs et des détails de mise en œuvre.

Le script utilise Microsoft.Web.La publication.cibles, de sorte que la plupart des propriétés standard doit toujours fonctionner. Voici quelques façons que vous pouvez utiliser:

# Convention based
msbuild PackageDeploy.build /p:PublishProfile=Stage;WebPublishPipelineProjectName=Name_of_your_web_application

# Absolute paths to profile + package
msbuild PackageDeploy.build /p:PublishProfile=Path\To\Profile.pubxml;PackageFileName=Path\To\Package.zip;WebPublishPipelineProjectName==Name_of_your_web_application

Si vous utilisez VS2012, assurez-vous de déclarer VisualStudioVersion=v11.0 à importer le bon fichier de l'éditeur.

L'aide de ce script, vous ne devriez pas avoir besoin de vérifier de nouveau votre application web dans la suite des étapes du déploiement d'un pipeline. Vous aurez juste besoin de garder les objets suivants après la construction/paquet étape:

• PackageDeploy.construire (ci-dessous)
• Vos profils de publication
• L'application web package zip

Voici le code source pour PackageDeploy.construire:

<!--
This build script supports deployment of a website package to a publish profile without rebuilding the project or package
If placed in the same directory as a web project that uses publish profiles, the following arguments will need to be defined:
Convention based required arguments:
PublishProfile: the name of the publish profile (or a path to a pubxml file if using non-convention based)
Configuration: Debug/Release
Convention based optional arguments:
VisualStudioVersion: Property specific to this build script that determines which WPP version to use (v10.5 [default] for VS2010+Azure updates, v11.0 for VS2012)
WebPublishPipelineProjectName:
WebPublishPipelineProjectDirectory: The root to the web project directory if this build script isn't there and PublishProfile isn't a path (to auto-detect publish profile directory)
Non-convention based optional arguments:
PackageFileName: The full path to the website package zip
UseDeclareParametersXMLInMsDeploy: true to save the parameters to a file and then use that file; false to inline the parameters
UseMsDeployExe: true to use msdeploy.exe; false to use the VS MSBuild task
-->
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="DeployFromPackage">
<PropertyGroup>
<!-- IMPL: Set this to v11.0 to use VS2012 -->
<VisualStudioVersion>v10.5</VisualStudioVersion>
</PropertyGroup>
<PropertyGroup>
<!-- IMPL: Declared in Microsoft.Web.Publishing.targets, but we need to declare PublishProfileRootFolder before it's imported -->
<WebPublishPipelineProjectDirectory Condition="'$(WebPublishPipelineProjectDirectory)'==''">$(MSBuildProjectDirectory)</WebPublishPipelineProjectDirectory>
<!-- IMPL: Usually detected by ".csproj" vs ".vbproj", but PackageDeploy.build is neither -->
<PublishProfileRootFolder Condition="'$(PublishProfileRootFolder)' == '' and Exists('My Project\PublishProfiles')">$(WebPublishPipelineProjectDirectory)\My Project\PublishProfiles</PublishProfileRootFolder>
<PublishProfileRootFolder Condition="'$(PublishProfileRootFolder)' == '' and Exists('Properties\PublishProfiles')">$(WebPublishPipelineProjectDirectory)\Properties\PublishProfiles</PublishProfileRootFolder>
</PropertyGroup>
<!-- IMPL: Select the correct version of Microsoft.Web.Publishing.targets (usually done by the csproj via WebApplication.targets) -->
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\$(VisualStudioVersion)\Web\Microsoft.Web.Publishing.targets" />
<!-- FIX: MSDeployPublish depends on building the package (can be skipped by clearing MSDeployPublishDependsOn) -->
<!-- IMPL: ImportPublishingParameterValues transforms all the MSDeployParameterValue+ParameterValue to MsDeployDeclareParameters+Value -->
<Target Name="DeployFromPackage" Condition="'$(PublishProfile)' != ''" DependsOnTargets="ImportPublishingParameterValues">
<PropertyGroup>
<_PublishMsDeployServiceUrl>$(MsDeployServiceUrl)</_PublishMsDeployServiceUrl>
<_PublishMsDeployServiceUrl Condition="('$(MSDeployPublishMethod)'=='INPROC')"></_PublishMsDeployServiceUrl>
</PropertyGroup>
<ItemGroup>
<!-- IMPL: Always uses "package" source -->
<MsDeploySourceProviderSetting Remove="@(MsDeploySourceProviderSetting)" />
<MsDeploySourceProviderSetting Include="package">
<Path>@(_MSDeployPackageFile->'%(FullPath)')</Path>
<EncryptPassword>$(DeployEncryptKey)</EncryptPassword>
<WebServerAppHostConfigDirectory>$(_MSDeploySourceWebServerAppHostConfigDirectory)</WebServerAppHostConfigDirectory>
<WebServerManifest>$(_MSDeploySourceWebServerManifest)</WebServerManifest>
<WebServerDirectory>$(_MSDeploySourceWebServerDirectory)</WebServerDirectory>
</MsDeploySourceProviderSetting>
<MsDeployDestinationProviderSetting Remove="@(MsDeployDestinationProviderSetting)" />
<MsDeployDestinationProviderSetting Include="auto">
<Path></Path>
<ComputerName>$(_PublishMsDeployServiceUrl)</ComputerName>
<UserName>$(UserName)</UserName>
<Password>$(Password)</Password>
<EncryptPassword>$(DeployEncryptKey)</EncryptPassword>
<IncludeAcls>False</IncludeAcls>
<AuthType>$(AuthType)</AuthType>
<WebServerAppHostConfigDirectory>$(_MSDeployDestinationWebServerAppHostConfigDirectory)</WebServerAppHostConfigDirectory>
<WebServerManifest>$(_MSDeployDestinationWebServerManifest)</WebServerManifest>
<WebServerDirectory>$(_MSDeployDestinationWebServerDirectory)</WebServerDirectory>
</MsDeployDestinationProviderSetting>
</ItemGroup>
<!--Debug/Diagnostic message is not localized-->
<Message Text="MSDeployPublish MsDeploySourceProviderSetting is @(MsDeploySourceProviderSetting)" Condition="$(EnablePackageProcessLoggingAndAssert)" />
<Message Text="MSDeployPublish MsDeployDestinationProviderSetting is @(MsDeployDestinationProviderSetting)" Condition="$(EnablePackageProcessLoggingAndAssert)"/>
<ExportParametersFile
Condition="!$(UseDeclareParametersXMLInMsDeploy) And $(EnablePackageProcessLoggingAndAssert)"
Parameters="@(MsDeployDeclareParameters)"
DeclareSetParameterFile="$(PackageLogDir)\MSDeployPublish.parameters.xml"
GenerateFileEvenIfEmpty="True"
/>
<!--First delete the ParameterFile-->
<Delete Files="$(PublishParametersFile)"  Condition="Exists($(PublishParametersFile))" ContinueOnError="true"/>
<!-- FIX: Use SetParameterFile (rather than DeclareSetParameterFile), which isn't used anywehere in Microsoft.Web.Publishing.targets -->
<ExportParametersFile
Parameters="@(MsDeployDeclareParameters)"
SetParameterFile="$(PublishParametersFile)"
GenerateFileEvenIfEmpty="True"
Condition="$(UseDeclareParametersXMLInMsDeploy)"
/>
<PropertyGroup>
<_VsPublishParametersFile></_VsPublishParametersFile>
<_VsPublishParametersFile Condition="$(UseDeclareParametersXMLInMsDeploy) and '$(_VsPublishParametersFile)'==''">$(PublishParametersFile)</_VsPublishParametersFile>
</PropertyGroup>
<ItemGroup Condition="!$(UseDeclareParametersXMLInMsDeploy)">
<_VsPublish_MsDeployDeclareParameters Remove="@(_VsPublish_MsDeployDeclareParameters)" />
<_VsPublish_MsDeployDeclareParameters Include="@(MsDeployDeclareParameters)" />
<!-- IMPL: Utilising the real version of this has way too much baggage (simplifying it could have repercussions, though) -->
<_VsPublish_MsDeployDeclareParameters Include="$(DeployParameterIISAppName)" Condition="'$(DeployIisAppPath)' != ''">
<Value>$(DeployIisAppPath)</Value>
</_VsPublish_MsDeployDeclareParameters>
</ItemGroup>
<!-- FIX: Microsoft.Web.Publishing.targets uses "SetParameterItems", which doens't appear to work. This uses SimpleSetParameterItems instead  -->
<VSMSDeploy
Condition="!$(UseMsdeployExe)"
MSDeployVersionsToTry="$(_MSDeployVersionsToTry)"
Source="@(MsDeploySourceProviderSetting)"
Destination="@(MsDeployDestinationProviderSetting)"
DisableLink="$(PublishDisableLinks)"
EnableLink="$(PublishEnableLinks)"
AllowUntrustedCertificate="$(AllowUntrustedCertificate)"
BuildingInsideVisualStudio="$(BuildingInsideVisualStudio)"
SkipExtraFilesOnServer="$(SkipExtraFilesOnServer)"
SkipRuleItems="@(MsDeploySkipRules)"
OptimisticParameterDefaultValue="$(EnableOptimisticParameterDefaultValue)"
SimpleSetParameterItems="@(_VsPublish_MsDeployDeclareParameters)"
ImportSetParametersItems="$(_VsPublishParametersFile)"
RetryAttempts="$(RetryAttemptsForDeployment)"
InvokedByPublish="true"
>
<Output TaskParameter="Result" PropertyName="_PublishResult" />
</VSMSDeploy>
<!-- FIX: Microsoft.Web.Publishing.targets uses "SetParameterItems", which doens't appear to work. This uses SimpleSetParameterItems instead  -->
<MSdeploy
Condition="$(UseMsdeployExe)"
Verb="sync"
Source="@(MsDeploySourceProviderSetting)"
Destination="@(MsDeployDestinationProviderSetting)"
DisableLink="$(PublishDisableLinks)"
EnableLink="$(PublishEnableLinks)"
EnableRule="$(MsDeployDoNotDeleteRule)"
AllowUntrusted="$(AllowUntrustedCertificate)"
SkipRuleItems="@(MsDeploySkipRules)"
OptimisticParameterDefaultValue="$(EnableOptimisticParameterDefaultValue)"
SimpleSetParameterItems="@(_VsPublish_MsDeployDeclareParameters)"
ImportSetParametersItems="$(_VsPublishParametersFile)"
RetryAttempts="$(RetryAttemptsForDeployment)"
ExePath="$(MSDeployPath)" />
</Target>
</Project>