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
Retire topic: Packages, Metapackages and Frameworks #1311
Comments
Indeed. I think the main sources of confusion are:
The concepts of "package" and "metapackage" I believe are clear to most. |
That topic needs serious and complete rewrite. It is the serious problem that the basics can't be outlined right. |
Agree wholeheartedly. We now have .NET Framework, .NET Core and now .NET Standards. To make matters worse, we now can reference bits and pieces of these together. My head hurts reading the above link. |
The first time I read the article I was confused. But after reading docs for .NET standard (and the fact that it's just a definition of APIs and not an implementation) and article about deployment methods for .NET core I was able to understand the article. Maybe it's better if some prerequisite material is defined at first. Or if a metaphor (like the LEGO metaphor in comments) is added to make it clearer. |
@tdykstra another one related to the terminology work |
@AmirHasanzade Metaphors rarely make technical concepts more understandable IMO, and the LEGO metaphor suggested by that comment is particularly vague and misaligned with what it tries to describe. Better IMO to explain the concepts in terms of what they really are, but clearly and exhaustively. |
Retire existing confusing doc. @tdykstra |
Topic URL: https://docs.microsoft.com/en-us/dotnet/articles/core/packages
Comments on this topic indicate that people are confused and they don't understand the terminology used and the concepts introduced.
The text was updated successfully, but these errors were encountered: