Skip to content
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

Closed
Rick-Anderson opened this issue Apr 5, 2018 · 3 comments
Closed

Document Microsoft.AspNetCore.App #5884

Rick-Anderson opened this issue Apr 5, 2018 · 3 comments
Assignees

Comments

@Rick-Anderson
Copy link
Contributor

Rick-Anderson commented Apr 5, 2018

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.

@guardrex
Copy link
Collaborator

Adding the blurb from the 2.1.0-preview2 roadmap blog post:

ASP.NET Core 2.1 will introduce a new meta-package for use by applications: Microsoft.AspNetCore.App. The new meta-package differs from the existing meta-package in that it reduces the number of dependencies of packages not owned or supported by the ASP.NET or .NET teams to just those deemed necessary to ensure the major framework features function. We will update project templates to use the new meta-package. The existing Microsoft.AspNetCore.All meta-package will continue to be made available throughout the 2.x lifecycle. For additional details see aspnet/Announcements#287.

@isaacrlevin
Copy link
Contributor

@Rick-Anderson @guardrex proposal to add a node in Fundamentals called MetaPackages that has

  • Microsoft.AspNetCore.App
  • Microsoft.AspNetCore.All

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

@Rick-Anderson
Copy link
Contributor Author

I'll think about that. I have it in PR, although not the TOC.
#6069

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants