Description
Removed Microsoft.AspNetCore.All shared framework
Earlier this year, we announced the Microsoft.AspNetCore.App metapackage (see aspnet/Announcements#287). That announcement said:
The existing Microsoft.AspNetCore.All meta-package will continue to be made available throughout the 2.x lifecycle, but we recommend customers move to the new Microsoft.AspNetCore.App meta-package and then add individual references to any of the removed packages if their app requires it.
See our documentation for details on how to migrate from Microsoft.AspNetCore.All to .App.
As of ASP.NET Core 3.0 we no longer produce the Microsoft.AspNetCore.All metapackage and the matching Microsoft.AspNetCore.All shared framework in the 3.0 nightly builds.
This package will still be available in ASP.NET Core 2.2 and will continue to receive servicing updates in ASP.NET Core 2.1.
Version introduced
3.0
Old behavior
Applications could use the Microsoft.AspNetCore.All metapackage to target the Microsoft.AspNetCore.All shared framework on .NET Core.
New behavior
There is no Microsoft.AspNetCore.All shared framework as part of .NET Core 3.0
Reason for change
As previously announced, the Microsoft.AspNetCore.All included a large number of external dependencies.
Recommended action
Migrate your app to use the Microsoft.AspNetCore.App framework. Components that used to be available in Microsoft.AspNetCore.All are still available on NuGet and will now be deployed with your app instead of being included in the framework.
Category
- ASP.NET Core
Affected APIs
Any API that was only present in the Microsoft.AspNetCore.All framework.
Issue metadata
- Issue type: breaking-change