title: Publish to IIS with new MSBuild for dotnet core?
body: <p>I'm trying to get an Azure Web App deployment working via Release Manager in VSTS. I know we had this in project.json prior to the migration to MSBuild for dotnet core 1.1:
  <div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-js lang-js prettyprint-override"><code>  "tools": {
      "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.1.0-preview4-final"
    },
  
    "scripts": {
      "postpublish": "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%"
    }</code></pre>
  </div>
  </div>
  </p>
  
  <p>Currently I'm using something like:
  dotnet publish --framework netcoreapp1.1 -c 'Release' -o 'C:\output'</p>
  
  <p>The web.config produced has:</p>
  
  <pre><code>&lt;aspNetCore processPath="dotnet" arugments=".\MyApp.Web.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" /&gt;
  </code></pre>
  
  <p>However, when this is deployed via Kudu to the Azure Web App, I receive an "HTTP 502.5 - Process Failure" exception from IIS. I assume this is because IIS does not understand this processPath. Locally I run exclusively through Kestrel because I've got other devs not working on Windows machines. </p>
  
  <p>Do I need to target the full .NET Framework on builds for deployment or is there something I'm missing to allow IIS running in Azure Web Apps to host a dotnet core 1.1 app?</p>