An assembly specified in the application dependencies manifest (Microsoft.AspNetCore.AzureAppServices.HostingStartup.deps.json) was not found

Jean-Philippe Berger 6

Hello,

I have a net core app service that has been running fine until yesterday.

It works when I run it locally, but azure fails to start it now.

![133209-image.png][1]

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

I am not sure how I am supposed to fix this, since it seems to be on the azure side.

Thank you,
Jean-Philippe

Takahito Iwasa 4,841 Reputation points MVP

2021-09-20T06:31:09.03+00:00

Hi.

I found a .NET Core 2.1 issue report.
Can you fix it like SO and give it a try?
https://stackoverflow.com/questions/69243168/azure-app-services-assembly-specified-in-application-dependencies-manifest-mic

1 answer

ajkuma 22,521 Reputation points Microsoft Employee

2021-09-21T08:42:27.973+00:00

@Jean-Philippe Berger , Thanks to @Takahito Iwasa for sharing the SO discussion thread, I was also checking/discussing on this internally.

To benefit the community, copying the steps suggested for fix (which worked for others):

1.Publish with:

<PublishWithAspNetCoreTargetManifest>False</PublishWithAspNetCoreTargetManifest>

2.Upgrade to .NET Core 2.2

See this blog - net-core-2-1-will-reach-end-of-support-on-august-21-2021 for more info.

If you still have further issues, please let us know I'll follow-up with you.

Apologies for any inconvenience with! Thanks for your patience.
Please sign in to rate this answer.

2 people found this answer helpful.
Jean-Philippe Berger 6 Reputation points

2021-09-21T14:28:10.977+00:00

Thanks for your reply, I ended up converting my application to Net Core 3.1 and it worked.

ajkuma 22,521 Reputation points Microsoft Employee

2021-09-21T19:14:50.48+00:00

JeanPhilippeBerger-3409, Glad you got it working. Thanks for sharing (converting app to Net Core 3.1) an update with the community. Much appreciate the follow-up.

Ian Robinson 1 Reputation point

2021-09-24T11:52:00.34+00:00

Hello,

Regarding this blog post -- https://devblogs.microsoft.com/dotnet/net-core-2-1-will-reach-end-of-support-on-august-21-2021/

which says

"When .NET Core 2.1 reaches end of support, applications that use this version will continue to run."

So is Azure an exception here? I had a production site go down with this issue and was "forced" to upgrade (which was a complicated and risky process given the scope/nature of the app).

Is this something Azure customers should expect to happen when a version reaches end of support?

Ian Robinson 1 Reputation point

2021-09-29T19:17:33.847+00:00

Hello @ajkuma , were you able to find out any more information when you checked on this internally?

ajkuma 22,521 Reputation points Microsoft Employee

2021-10-01T20:16:15.853+00:00

IanRobinson-5645, Apologies for the delay and inconvenience with this issue! There was an issue identified and it was mitigated. It was informed on Service Health for the affected users. Just copying the Service Health notification from my test subscription.

"
Summary of impact: Between 18:45 UTC on 15 Sep 2021 and 06:00 UTC on 22 Sep 2021, you were identified as a customer using Azure App Service who may have experienced failures or 502 errors when starting up the applications.

Root cause: We identified that a recent deployment removed the out-of-service ASP.NET CORE 2.1 from the platform which has caused the issue.

Mitigation: We rolled back the missing ASP.NET CORE 2.1 version, to mitigate the issue.

Stay informed about Azure service issues by creating custom service health alerts: https://aka.ms/ash-videos for video tutorials and https://aka.ms/ash-alerts for how-to documentation.

Ian Robinson 1 Reputation point

2021-10-01T20:34:10.57+00:00

Thanks for sharing. I'm copying this to my support representative. For some reason this doesn't show up in our Service Health.

ajkuma 22,521 Reputation points Microsoft Employee

2021-10-05T18:58:59.11+00:00

IanRobinson-5645, Thanks for the follow-up. As mentioned, the notification was sent to only affected users. Apologies for any inconvenience with this issue. If you're still experiencing the issue, please share the #SR ticket number I'll follow-up on this further internally.
Sign in to comment