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

Update library guidance #31175

Open
Jericho opened this issue Sep 14, 2022 · 2 comments
Open

Update library guidance #31175

Jericho opened this issue Sep 14, 2022 · 2 comments
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. Pri2

Comments

@Jericho
Copy link

Jericho commented Sep 14, 2022

In particular, the "Cross-platform targeting" section needs to be refreshed, I think.

  • What are the latest recommendations for library authors?
  • What are the most "reasonable" frameworks we should target if we want our library to be used by the largest audience? I realize this might be somewhat subjective but let's assume library authors want to reach developers who use "reasonably" up-to-date frameworks (in other words, let's ignore net45, netstandard1.x, etc.). For example, is net48;netstandard2.1;net5.0;net6.0 reasonable?
  • Does it make sense to continue targeting netstandard at all?
  • Is it redundant to target both net5 and net6? If so, I assume it makes more sense to only target net6, right?
  • How will these recommendations change when net7 is released?

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Sep 14, 2022
@gewarren gewarren added doc-enhancement Improve the current content [org][type][category] okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. labels Nov 10, 2022
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Nov 10, 2022
@ArthurHNL
Copy link

I would like to point out that .NET 5 is out of support by now. So this article is de-facto recommending to target a framework that is out of support, as it suggests adding a reference to net5.0 or later.

@Jericho
Copy link
Author

Jericho commented Feb 22, 2023

@gewarren I noticed that you are preparing a list of documents to update for .NET 8. Maybe the guidelines for library authors should also be on that list?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. Pri2
Projects
None yet
Development

No branches or pull requests

4 participants