Can't get a good deploy command to come out of this

[rmagruder]

Sayed, I hope you're seeing these updates...

Trying now for several days to get this to work, have run Google into the ground, and still getting nowhere. Maybe I'm just missing something important.

When I look at the command that gets run from Publish-Interactive.ps1, it's like this (redacted as needed)

C:\temp\MyService>"C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:archiveDir="C:\Users\RMAGRU1\AppData\Local\Temp\MyService_zip" -dest:auto,includeAcls='False',ComputerName='https://targetServer:8172/msdeploy.axd?site=Default Web Site?site=Default Web Site/MyService',Username=mydomain\myuser,Password=mypassword,AuthType='basic' -disableLink:AppPoolExtension -disableLink:ContentExtension -disableLink:CertificateExtens
ion -setParamFile:"C:\Users\RMAGRU1\AppData\Local\Temp\MyService_zip\SetParameters.xml" -skip:objectName=dirPath,absolutePath="Deploy" -skip:objectName=filePath,absolutePath=web...config -skip:objectName=dirPath,absolutePath=
Package -skip:objectName=filePath,absolutePath=._.wpp.targets$ -allowUntrusted -enableRule:DoNotDelete

The site doesn't exist on the server, but "Default Web Site" sure does. I have full rights to add sites, remote in, etc, from the user name I'm specifying, but the 'MyService' site doesn't exist.
I notice above that we get TWO "?site" parameters onto the .axd command line. I'm assuming that since "MyService" doesn't exist, that's causing the problem? It should just be going to "Default Web Site", but it seems like the IIS Web Application name is being appended to that, and thus breaking it. I have managed to get msdeploy to work from a regular command prompt from the same machine but that's using the dump from Visual Studio of its msdeploy.exe, using the manifest rather than the archive source.

I hope you have some thoughts, because I'm feeling like I'm dealing with a magic incantation instead of a piece of software, and I can't get the spell right.

[rmagruder]

This, by the way, is the publishconfiguration.ps1 file:

$settingsFromUser =@()
$settingsFromUser += @{name="IIS Web Application Name";value=''}
$settingsFromUser += @{name="Add write permission to App_Data Folder";value='Default Web Site/MyService/App_Data'}
$settingsFromUser += @{name="MyEntities-Web.config Connection String";value='metadata=res:///3DEntities.csdl|res:///3DEntities.ssdl|res://*/3DEntities.msl;provider=Devart.Data.Oracle;provider connection string=""User Id=user;Password=pw;Server=db;Direct=True;Sid=db;Port=1523;Persist Security Info=True""'}
$settingsFromUser += @{name="Computer name";value='https://myserver:8172/msdeploy.axd?site=Default Web Site'}
$settingsFromUser += @{name="Username";value='domain\user'}
$settingsFromUser += @{name="Password";value='pw'}
$settingsFromUser += @{name="Allow untrusted certificate";value='true'}
$settingsFromUser += @{name="whatif";value='false'}
$settingsFromUser += @{name="MSDeployDoNotDelete";value='true'}
$settingsFromUser += @{name="AuthType";value='basic'}
$settingsFromUser += @{name="ZipFile";value='MyService.zip'}
$settingsFromUser += @{name="TransformName";value='Dev'}

I tried blanking the IIS Web Application Name to try to stop the duplicate "?site=" from being in the computer name field, to no avail. I get the Default Web Site and then another ?site="Default Web Site/MyService" at the end of it, and it all blows up. I can make the deploy work by stealing the command line, editing it and removing the extra ?site= and leaving just "Default Web Site" as the ?site parameter, and running it from a VS command prompt. So it clearly isn't a permissions issue. It also seems to understand from somewhere what virtual to create, even though I blanked out the IIS Web Application Name variable.

[rmagruder]

Update, it appears the fix is the same as mentioned in

Remote deployment having "nested" site name fails #49

[sayedihashimi]

See my comments at #49 (comment)