Earlier this year, we announced the Microsoft.AspNetCore.App metapackage (see #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.
We have begun working on ASP.NET Core 3.0, and as a part of that, we will stop producing 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.
Please use dotnet/aspnetcore#3418 for questions or comments.
[This announcement has been migrated to: dotnet/docs#14962]
Earlier this year, we announced the Microsoft.AspNetCore.App metapackage (see #287). That announcement said:
See our documentation for details on how to migrate from Microsoft.AspNetCore.All to .App.
We have begun working on ASP.NET Core 3.0, and as a part of that, we will stop producing 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.
Please use dotnet/aspnetcore#3418 for questions or comments.
[This announcement has been migrated to: dotnet/docs#14962]