dotnet / dotnet/docs

Is it worth to mention use .net standard 2.1 for pure POCO project

Open
#28,739 1 comment 0 reactions 0 assignees View on GitHub
:watch: Not Triaged dotnet/svc standard-library/subsvc
Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
19h 10m
Merged PRs (30d)
268

Description

For this section: [.NET Standard not deprecated](https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-1-0#net-standard-not-deprecated)

Many companies have a pure POCO project, just as a Model project that is consumed between different other projects, for this case, does .NET Team consider keeping targeting .NET Standard 2.1 for the POCO project instead of targeting to .NET 6.

The benefit of targeting to .NET Standard 2.1 will maintain the compatibility, and the POCO project doesn't really benefit from any feature/performance improvement from .NET 6.

But upgrading the shared POCO project to .NET 6 will force all other projects to upgrade to .NET 6 too.

So I am wondering do we need to add another entry to say "If the POCO project doesn't use any new types from the latest .NET version, keep it to .NET Standard to maintain the best compatibility and avoid forcing any consuming projects to upgrade to the same level"?

---
#### Document Details

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

* ID: 9eb8b774-c6f0-8235-6964-15219baf2ea7
* Version Independent ID: 6819a4a7-7527-d8c7-e132-767f7344e00e
* Content: [.NET Standard](https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-1-0#net-standard-not-deprecated)
* Content Source: [docs/standard/net-standard.md](https://github.com/dotnet/docs/blob/main/docs/standard/net-standard.md)
* Product: **dotnet**
* Technology: **dotnet-standard**
* GitHub Login: @gewarren
* Microsoft Alias: **gewarren**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.