msdeploy

问题 Can anyone confirm (preferably with a link to docs) whether MSDeploy packages are uploaded in their entirety before the files are sync'd or does the sync occur between msdeploy.exe and msdeploy.axd (with only modified files being uploaded)? Or, to put it another way, if I have a 1GB package zip that only contains 1MB worth of changed files will msdeploy upload the entire 1GB package to MsDeploy.axd and perform the sync on the server or will it only upload the 1MB worth of changed files? 回答1:

问题 When publishing to our Azure Web App using the following Powershell script, we often have issues whereby files from the previous publish cause runtime errors. param($websiteName, $packOutput) $website = Get-AzureWebsite -Name $websiteName # get the scm url to use with MSDeploy. By default this will be the second in the array $msdeployurl = $website.EnabledHostNames[1] $publishProperties = @{'WebPublishMethod'='MSDeploy'; 'MSDeployServiceUrl'=$msdeployurl; 'DeployIisAppPath'=$website.Name;

问题 This question has been danced around a bit, forgive me if it is a duplicate but I haven't been able to find an exact answer. I am trying to create a Parameters.xml for deployment configuration that specifies the destination physical file folder for a web site. This is for an automated build using TeamCity, e.g. commandline using .deploy.cmd. Can someone explain what I need to do? Parameters.xml: <parameter name="physicalPathLocation" description="Physical path where files for this Web service

问题 This question has been danced around a bit, forgive me if it is a duplicate but I haven't been able to find an exact answer. I am trying to create a Parameters.xml for deployment configuration that specifies the destination physical file folder for a web site. This is for an automated build using TeamCity, e.g. commandline using .deploy.cmd. Can someone explain what I need to do? Parameters.xml: <parameter name="physicalPathLocation" description="Physical path where files for this Web service

问题 I have a publish profile set up in a VS 2012 project. When I right click on the project in VS, select Publish and click on the [Publish] button, it publishes the project to the server using the settings provided in the Publish Profile. When I use msbuild and the command line, with the following syntax: msbuild.exe .\mvc.csproj /p:PublishProfile=DevServer /p:DeployOnBuild=True /p:Password=MyPassword /p:AllowUntrustedCertificate=true Then it builds the project, and gives me a message: Package

问题 So I have the following requirements: 1. Compile a large MVC app and pre-compile all of its views. 2. Run transforms for web.config 3. Package and publish for deployment into Azure Web Role I can do 1 with a modified proj file, 2 works if I us msdeploy, and 3 works fine when I use the VS 2012 Azure tools. Now I want to put these all together into a scripted process. Has anyone already done the leg work to get this running? 回答1: 1) /p:PrecompileBeforePublish=true 2 + 3) You need to add the

问题 I'm trying to create a web deploy package using msbuild through command line. I have been searching all over and found the following command msbuild myproject.csproj /t:package Though it works for me but it gives me only what visual studio gives us back when we create web deploy package through Packge/Publish Web tab with "only files needed to run this application" option selected from the drop down menu. But I want my web deploy package to look exactly the same as what I get when I select

问题 I have a Web Deploy 3.5 package that I want to deploy to a remote server. How do I specify the name of the site on the MSDeploy.exe command line? Here's what I have so far: C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe -source:package='package.zip' -dest:auto,computerName="ServerName",includeAcls="False" -verb:sync -disableLink:AppPoolExtension -disableLink:ContentExtension -disableLink:CertificateExtension -setParamFile:"package.SetParameters.xml" But the name of the site

问题 When using msdeploy and the msdeploy.axd handler any attempts to deploy to my remote server is met with a 401 not authorized error and the server logs IISWMSVC_AUTHORIZATION_SERVER_NOT_ALLOWED Only Windows Administrators are allowed to connect using a server connection. Other users should use the 'Connect To Site or Application' task to be able to connect. Process:WMSvc What is the correct way to target the axd for the site level? 回答1: If you use Web Deploy Tool 2.0 you can use IIS Manager UI

问题 I've configured TFS 2010 to do a build and utilizing the MSBuild arguments, have it deploying to a single server without any issues. /p:DeployOnBuild=True /p:Configuration=Development /p:DeployTarget=MSDeployPublish /p:MSDeployPublishMethod=RemoteAgent /p:MsDeployServiceUrl=http://<insert>/msdeployagentservice /p:username=<insert> /p:password=<insert> However, I am now to the point where I'd like to deploy to multiple machines after a build. I wasn't sure if there were some built in