Troubleshooting Msdeploy issues using Fiddler

JeremyBrooks

This past week I was troubleshooting an issue with Msdeploy and needed Fiddler to proxy MsDeploy. I eventually figured out how to get this working.

  1. In the msdeploy.exe.config ( “C:\Program Files\IIS\Microsoft Web Deploy V3”) add the piece that is in bold below.

<configuration>

<startup  useLegacyV2RuntimeActivationPolicy=”true” >

<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″ />

<supportedRuntime version=”v2.0.50727″ />

</startup>

  <system.net>

    <defaultProxy useDefaultCredentials=”true” enabled=”true”>

      <proxy autoDetect=”false” bypassonlocal=”false” proxyaddress=”http://127.0.0.1:8888” usesystemdefault=”false” />

    </defaultProxy>

  </system.net>

</configuration>

2. I used the command below to use Msdeploy to push my package to an Azure Web App. Its essentially the same process that VS uses to deploy. Make sure to have the -allowUntrusted switch so it doesn’t fail due to the proxy setting.

C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe” -verb:sync -source:contentPath=’C:\application’ -dest:contentPath=’jebrook-webapp-staging’,ComputerName=’https://jebrook-webapp-staging.scm.azurewebsites.net/msdeploy.axd’,UserName=”$jebrook-webapp-staging”,Password=”xxxx”,IncludeAcls=”False”,AuthType=”Basic” -enablerule:AppOffline -enableRule:DoNotDeleteRule -retryAttempts:20 -verbose -allowUntrusted

3.  Also make sure to allow Fiddler to decrypt the HTTPS traffic.