Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
SDK regression in 3.0.101 and 3.1.100 for ASP.NET Core workloads #17973
SDK regression in 3.0.101 and 3.1.100 for ASP.NET Core workloads
The 3.0.101 and 3.1.100 versions of the .NET Core SDK have a regression which potentially causes 2.2 and 3.0/3.1 dependencies to mismatch, causing applications to fail to start when running with IIS InProcess.
For the official announcement, see aspnet/Announcements#398.
.NET Core SDK 3.0.101
.NET Core SDK 3.1.100
In 3.0, we introduced the concept of a
However, in 3.0.1 and 3.1.0, we introduced a regression which removed a few select references from the
Libraries that were removed from the
Libraries that were added to the PlatformManifest.txt between 3.0.0 and 3.0.1:
The libraries that were added to the
If an application references (directly or transitively) a previous version of the
Users may work around this issue by doing one of the following:
Remove all direct and indirect references to the affected packages.
The following packages include the
Other affected libraries are contained in packages with the same name. See the above lists.
The resolution is to remove these package references from your application. Be aware that they may be transitive dependencies (dependencies of other packages you depend upon).
Avoid publishing incorrect package content
If you cannot remove earlier versions of the pacakges, you can explicitly suppress those packages from publishing using
<Project Sdk="Microsoft.NET.Sdk.Web"> <PropertyGroup> <TargetFramework>netcoreapp3.1</TargetFramework> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.AspNetCore.Server.IIS" Version="2.2.6" ExcludeAssets="All" /> </ItemGroup> </Project>
We recommend clearing out bin/obj folders before building with the above fix.
We are not sure if the problem we are running into currently is related to this issue. (Identity Server project runs without a problem iun dev mahcine but fails to start in Azure App Service instance. It was working a couple of weeks ago...) Could you provide more information about the symptoms caused by this regression?
I am trying to migrate my projects from .net core 2.2 to 3.1. And the problem was occurred when trying to publish the apps in IIS
For more details please see my question on stackoverflow: link
What is the root of a problem? I've tried everything, nothings seems to work :(
@Pilchie I tried it. It doesn't help at all. I know that the problem is occurred when I build the solution with a command:
And then publish the app with --no-build param:
And then when server tried to run the app, the error is occurred
The interesting thing is that when I publish app without
Maybe I could not understand how to use the commands, but my aim is to build the whole solution, and then publish the project on IIS without build in Framework Dependent Executable (FDE) mode. The target platform for me can be either linux-64 (CentOS) or win-x64. Should I have to change the commands?
This problem has not been reproduced when I use .net core 2.2 sdk and .net core 2.2 apps. The app has been published and run successfully. Feel a little bit confused