/ Announcements Public
Known issue in 3.0.2 and 3.1.1 for ASP.NET Core #401
Announcements related to ASP.NET Core 3.0
Announcements related to ASP.NET Core 3.1
Packages and Shared Framework
If your project has a package reference that transtively references certain assemblies in the Microsoft.AspNetCore.App shared framework
that are also available as NuGet packages and executes on a runtime other than 64-bit Windows, you will receive a runtime exception at the time the assembly is loaded with a message like:
Reference the package for the assembly which is failing to load explicitly in your application.
List of assemblies impacted:
Alternatively, if you use the Microsoft.AspNetCore.Identity.UI package and executes on a runtime other than 64-bit Windows, you will receive a runtime exception at the time the Microsoft.AspNetCore.Http.Features assembly is loaded with a message like:
Reference the Microsoft.AspNetCore.Http.Features package explicitly in your application.
Azure App Service
Note that by default Azure App Service runs websites in an x86 Windows environment, so you might see these issues when you deploy to
Azure App Service, even if your app works locally on your 64-bit Windows development machine. To workaround, you can either apply one of
the workarounds above or configure your app to run in a 64-bit environment. See the documentation for details.
Updating packages without updating shared runtime
If you update some packages to version 3.1.1, but don't have the 3.1.1 shared runtime installed, you may end up with an error like the below:
Ensure that you have the 3.1.1 shared runtime installed when updating packages. If you are using Razor runtime compilation, you may also need:
The text was updated successfully, but these errors were encountered: