IIS WebDeploy using MS Build Fails with error MSB4044 -ConcatFullServiceUrlWithSiteName task

Question

In setting up a Jenkins deployment job, I kept running into this error when trying to deploy a Visual Studio 2012 Web project via the command line.

error MSB4044: The "ConcatFullServiceUrlWithSiteName" task was not given a value for the required parameter "SiteAppName"

For reference, here are the parameters that I used:

/p:Configuration=Release /t:Rebuild  /p:VisualStudioVersion=11.0 /p:PublishProfile="DeployToDevServer" 
/p:DeployOnBuild=True /p:DeployTarget=MSDeployPublish 
/P:AllowUntrustedCertificate=True /p:MSDeployPublishMethod=WMSvc
/p:MsDeployServiceUrl=https://devmachine.server.com:8172/MsDeploy.axd 
/p:username=domainhere\adminuserhere /p:password=adminpasshere

Note: It would deploy just fine if I chose Publish... from inside the project.

Adrian Carr · Accepted Answer · 2013-08-09 17:30:20Z

7

After much googling, and finally comparing a project that would deploy with the one that wouldn't, I finally figured it out after I opened the .csproj files with a text editor and compared them. In the project that worked, I found this section:

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">

And it had this line:

<DeployIisAppPath>Default Web Site/sitenamehere</DeployIisAppPath>

I added this same line to the non-working project, changed the sitename, and it worked. Hope this helps someone else.

answered Aug 9, 2013 at 17:30

Adrian Carr

3,1231 gold badge37 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

malckier Over a year ago

I added just the sitename as was configured in IIS and this worked for me (without 'Default Web Site')

The Muffin Man Over a year ago

You would only need to do Default Web Site/sitenamehere if sitenamehere is an application under Default Web Site. If you add a new website that is a sibling of Default Web Site then it would just be sitenamehere.

SliverNinja · Accepted Answer · 2018-07-10 16:18:52Z

6

You could pass this DeployIisAppPath as parameter to Jenkins, like this: p:DeployIisAppPath=Default Web Site/sitenamehere This would allow you to have different sitenames on different machines. While in your example (with CSPROJ modification) you would be obliged to have one IIS site name on all target machines

edited Jul 10, 2018 at 16:18

SliverNinja

31.7k12 gold badges121 silver badges182 bronze badges

answered Aug 15, 2013 at 14:22

Anton Kuryan

6076 silver badges22 bronze badges

2 Comments

Roboblob Over a year ago

This is actually correct way to do it if you want to deploy via command line or TeamCity server. /p:DeployIISAppPath worked for me. THANK YOU!

Chaim Eliyah Over a year ago

This is a little unclear. This is an MSBuild parameter, not a Jenkins or TeamCity specific setting. Thanks!

Collectives™ on Stack Overflow

IIS WebDeploy using MS Build Fails with error MSB4044 -ConcatFullServiceUrlWithSiteName task

2 Answers 2

2 Comments

2 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Linked

Related