HTTP Error 502.5 - Microsoft.AspNetCore.Antiforgery.dll

[alaminut]

I've deployed my Asp.Net Core 2.0 app to a new Azure Web App from Visual Studio 2017 publish tool.

When I open up my application it gives me 502.5 error and does not start, I enabled logging and found out this error is logged:

Error:
An assembly specified in the application dependencies manifest (Epiverita.UI.deps.json) was not found:
package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'

This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
aspnetcore-store-2.0.3.xml

Application works perfectly fine on local development environment, and just in case I added above dependency as a seperate NuGet package - it is normally included in Microsoft.AspNetCore.All package - but I still get this error.

How can I solve this?

---

Resolution

EDIT by @natemcmaster May 18, 2018: this error happens when deploying to a machine that is missing the ASP.NET Core package runtime store. Please ensure your target machine has been updated to the latest version of ASP.NET Core 2.0.x. See https://www.microsoft.com/net/download/all for downloads. If you are still having issues, please open a new bug on https://github.com/aspnet/Home.

[dcarr42]

2.0.3 has only been published for a day....kudo in and attempt a dotnet restore.

[alaminut]

Sorry I didn't understand what you mean by restore?

[dcarr42]

If you attempt a dotnet restore/build up in Azure you might be able to isolate the issue.

[dcarr42]

dotnet/aspnetcore#2254

[MitchellNZ]

Running into the same issue myself..

Error I'm getting from Kudu when trying to manually dotnet run is:

Error:
  An assembly specified in the application dependencies manifest (APP_NAME.deps.json) was not found:
    package: 'Microsoft.AspNetCore.ApplicationInsights.HostingStartup', version: '2.0.1'
    path: 'lib/netcoreapp2.0/Microsoft.AspNetCore.ApplicationInsights.HostingStartup.dll'

  This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
    aspnetcore-store-2.0.3.xml

I am using the Microsfot.AspNetCore.All package (which appears to include this package mentioned above).
I have also tried manually including the package.. But no luck.

I am out of ideas now.. if anyone could point me in the right direction, would be much appreciated.
Thanks!

[robpearson]

I hit this as well and I fixed it by following the instructions in this comment.

The problem is the ASP.NET web app is using the host server package store and the Azure one hasn't been updated as needed. The solution is to add <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest> to your csjproj files so the dotnet publish bundles all the required files. Mine now looks like this:

<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
  </PropertyGroup>
...

More info here.

I build my web apps w/ TeamCity and ship w/ Octopus Deploy and that's the only change I needed.

[alaminut]

Fixed this issue with @robpearson's suggested solution. Running dotnet restore on Kudu did not solve it. Any ETA on when will Azure package store be updated?

[sebastianbk]

I am still having this issue when publishing to Azure Web Apps. I followed @robpearson's advice and adding the PublishWithAspNetCoreTargetManifest property and setting it to false. However, when navigating to my Azure Web App, I still see the 502.5 error. What else could be wrong?

Here is a dump of my csproj file: https://pastebin.com/1CfNKcRb

@Eilon, can you maybe help out on this one? It's pretty critical to our business.

[Eilon]

@muratg - do you know the status of getting Azure apps working with this? Also cc @JunTaoLuo in case you know about this.

[muratg]

@sebastianbk What does your publish output look like when you set that property and do a restore? It should have a lot of assemblies with the property set to false.

Also, what's your deployment mechanism to App Service?

[sebastianbk]

Hi @muratg. Here is the output of dotnet publish -c Release: https://pastebin.com/FJS5z8hP

I have both tried using Web Deploy from Visual Studio (15.4.4) as well as dragging and dropping in all the files via Kudu.

[muratg]

Files seem to be present in your publish output. @JunTaoLuo Any thoughts?

[JunTaoLuo]

@sebastianbk would you be able to share your logs with us? You can turn it on by modifying the web.config by setting stdoutLogEnabled to true and creating the logs directory adjacent to your application dll

<aspNetCore processPath="dotnet" arguments=".\App.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />