title: Asp.Net Core 2.0 on Azure results in a 502.5
body: <p>I have a small web app developed with Asp.Net Core 1.1 deployed on Azure and it works well. I just migrated the project to use Asp.Net Core 2.0 and tried to deploy it on Azure. The deployment went fine but when I open the site, I get a 502.5 error. When I check my Azure log stream, I get the following error:</p>
  
  <blockquote>
    <p>This error occurs when a CGI application does not return a valid set
    of HTTP headers, or when a proxy or gateway was unable to send the
    request to a parent gateway. You may need to get a network trace or
    contact the proxy server administrator, if it is not a CGI problem.</p>
  </blockquote>
  
  <p>Useless to say that it works well on my development machine with the same code. Note that I'm also using Entity Framework Core 2.0 although I deactivated the database creation on Azure (to check if it was not the cause).</p>
  
  <p>For information, the way I migrated from 1.1 to 2.0 is by changing the target framework settings to "netcoreapp2.0" and by using the NuGet package "Microsoft.AspNetCore.All". Just to be sure, I also deleted my publish profile and recreate one.</p>
  
  <p>Is it possible that Asp.Net Core 2.0 is not yet available on Azure ? I'm fairly new to Asp.Net Core, so I don't know when new releases are made available on Azure.</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>When I try to run my app with dot net CLI via the debug console as proposed by natemcmaster, I got the following issue:</p>
  
  <blockquote>
    <p>Unhandled Exception: System.IO.FileLoadException: Could not load file
    or assembly 'Microsoft.AspNetCore.Hosting.Abstractions,
    Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
    The located assembly's manifest definition does not match the assembly
    reference. (Exception from HRESULT: 0x80131040)</p>
  </blockquote>
  
  <p>I downloaded the DLL on my desktop and check the version with Dot Net Peak and indeed, the DLL is 1.1.2, although I created the project with Visual Studio and directly publish it, so is it an issue with Visual Studio ? Or Nuget ?</p>