对MSBuild参数的DeployIisAppPath设置有什么期望？ [英] What is expected for DeployIisAppPath setting on MSBuild argument?

问题描述

SERVERNAME(myDomain\Username)
   Application Pools
   Sites
      DEV Site1
      DEV Site2
      dev Site 3
         bin
         Content
         ...
         Views
      etc ...

这是我的DEV Web服务器的基本布局。我们的DEV Web服务器上运行着许多站点。我正在尝试使用TFS 2013 Build将我的网站发布到DEV服务器，之后来自 Vishal Joshi ， Microsoft 和其他人。

This is my basic layout of our DEV web server. Our DEV web server has many sites running on it. I am trying to use TFS 2013 Build to publish my web site to the DEV server following articles from Vishal Joshi, Microsoft and others.

我的错误是 ERROR_SITE_DOES_NOT_EXIST 。基本修复对我没有帮助。

My error is "ERROR_SITE_DOES_NOT_EXIST". The basic fix does not help me.

在我的例子中，我正在使用 / p：DeployIisAppPath =dev Site 3。该站点下没有定义任何应用程序。

In my example, I'm using /p:DeployIisAppPath="dev Site 3". There are no applications defined under the site.

微软的说明没用。我以为我应该只使用IIS站点名称，但这并不能证明是成功的。此参数的预期值是多少？我有人需要应用程序池名称吗？是否有一个命令可以针对IIS发出以导出所有可用的AppPath列表？一旦我在DEV服务器上解决这个问题，我就必须对STG服务器做同样的事情。

Microsoft's instructions are useless. I thought I should just use the IIS site name, but that is not proving successful. What is the value expected for this parameter? Do I someone need the App Pool name? Is there a command I can issue against IIS to export the list of all the AppPaths available? Once I figure this out on the DEV server, I have to do the same with the STG server.

[更新1]
添加完整的MSBuild参数

[UPDATE 1] Adding the full MSBuild arguments

/p:DeployOnBuild=True 
/p:DeployTarget=MsDeployPublish 
/p:CreatePackageOnPublish=True 
/p:MSDeployPublishMethod=InProc 
/p:MSDeployServiceUrl=http://SERVER:PORT/MsDeployAgentService
/p:DeployIisAppPath="dev Site 3"

推荐答案

您的服务器位于您的域内，因此我将使用我的内部服务器解决方案。我必须为我们的DMZed服务器提供不同的东西。

Your server is inside your domain, so I will use the solution that I have for our inside server. I had to come up with something different for our DMZed servers.

/p:DeployOnBuild=True 
/p:DeployTarget=MsDeployPublish 
/p:CreatePackageOnPublish=False 
/p:MSDeployPublishMethod=WMSvc 
/p:MsDeployServiceUrl="https://SERVER:8172/MsDeploy.axd?Site=direct" 
/p:DeployIisAppPath="direct" 
/p:AllowUntrustedCertificate=True 
/p:AuthType=NTLM 
/p:UserName=

此解决方案使用WMSvc（安装在网络服务器上）来允许TFS构建进程以访问部署时所需的服务器部分。我没有尝试过MSDeployAgentService，所以我不确定那个。在我的情况下，我没有在部署时创建一个包（我似乎记得当我这样做时它返回了一个错误，虽然我不记得它是什么）。

This solution uses WMSvc (installed on the webserver) to allow the TFS build process to access the portions of the server that it needs to when deploying. I havent tried MSDeployAgentService, so i am unsure about that one. In my case, I do not create a package on deploy ( I seem to recall it returned an error when I did that, although I don't remember what it was).

此外，最后三个参数对于TFS Build Service帐户登录VMSvc并执行其操作是必要的。将UserName留空会导致它以正在运行的帐户登录（不需要提供密码，是的！）。

Also, last three arguments are necessary to for the TFS Build Service account to log into VMSvc and do its thing. Leaving UserName blank causes it to log in as the running account (no need to supply a password, yay!).

以下是成功部署时构建日志的示例输出。

Here is an example output from the build log on a successful deployment.

   MSDeployPublish:
     Start Web Deploy Publish the Application/package to https://SERVER:8172/MsDeploy.axd?Site=direct ...
     Starting Web deployment task from source: manifest(C:\Builds\1\Direct\Continuous Integration (SERVER)\Binaries\_PublishedWebsites\WEBPROJECTNAME_Package\Archive.SourceManifest.xml) to Destination: auto().
     Adding ACL's for path (direct)
     Adding ACL's for path (direct)
     Updating file (direct\bin\Content\images\buttonBkgHover.png).
          ... Removed for brevity => This section is all 'Updating file (PATH).'
     Updating file (direct\Web.config).
     Adding ACL's for path (direct)
     Adding ACL's for path (direct)
     Successfully executed Web deployment task.
     Publish is successfully deployed.
   PipelineDeployPhase:
     Publish Pipeline Deploy Phase

这篇关于对MSBuild参数的DeployIisAppPath设置有什么期望？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！