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 #398
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 discussion see dotnet/aspnetcore#17973.
.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.