-
Notifications
You must be signed in to change notification settings - Fork 25.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Microsoft.AspNetCore.App #5884
Comments
Adding the blurb from the 2.1.0-preview2 roadmap blog post:
|
@Rick-Anderson @guardrex proposal to add a node in Fundamentals called MetaPackages that has
Will need to update the All doc to mention starting with 2.1 it is recommended to move to App. App doc is new doc |
I'll think about that. I have it in PR, although not the TOC. |
Consider working with Andrew Lock and his blog
related #5314
Update Microsoft.AspNetCore.All metapackage to point out the App meta package is the recommended package.
See:
At 2.10 recommend .APP
aspnet/MetaPackages#255
the new meta-package includes version restrictions, such that other packages you might bring in, can't unintentionally upgrade bits of what's in Microsoft.AspNetCore.App higher than the version included. This helps to ensure a more reliable experience, as it becomes harder to end up with untested version combinations of related bits being used together in the same app (a large cause of customer issues today, given it often happens completely silently). You'll still be able to force it in the cases you want to do so (by lifting the affected package references to be direct in your project) but at that point you're effectively in an unsupported state.
The text was updated successfully, but these errors were encountered: