Choosing the target version of a .NET Standard library involves several considerations to ensure compatibility and functionality across different .NET implementations. Here are the key points to consider:
1. Compatibility with .NET Implementations
.NET Standard is designed to provide a uniform set of APIs that all .NET implementations must support. The version of .NET Standard you choose determines which .NET implementations and versions your library can run on. Higher versions of .NET Standard include more APIs but are supported by fewer .NET implementations.
.NET Standard 2.0: This version is widely recommended because it is supported by all modern platforms, including .NET Core, .NET Framework, and Xamarin. It provides a broad set of APIs and ensures compatibility with a wide range of applications[1].
.NET Standard 2.1: This version includes additional APIs but is not supported by .NET Framework. It is suitable if you do not need to support .NET Framework and want to take advantage of the latest APIs available in .NET Core and other modern .NET implementations[1].
2. API Requirements
Consider the APIs your library needs. If your library requires APIs that are only available in higher versions of .NET Standard, you will need to target that version. However, this may limit the number of platforms your library can run on.
3. Platform Support
Evaluate the platforms you need to support. If you need to support older platforms or a wide range of platforms, targeting a lower version of .NET Standard (such as 1.x) might be necessary. However, this comes with the trade-off of fewer available APIs and potentially more complex dependency management[1].
4. Future-Proofing
.NET Standard 2.0 is a stable choice for most libraries, as it is supported by all modern platforms and provides a good balance of API availability and compatibility. Since there will be no new versions of .NET Standard after 2.1, targeting .NET Standard 2.0 ensures long-term stability and broad compatibility[1].
5. Development Tools and Environment
Ensure that your development environment supports the .NET Standard version you choose. For example, Visual Studio 2017 version 15.3 or later is required to build .NET Standard 2.0 libraries[1].
Example Decision Process
Assess Platform Requirements: Determine the platforms your library needs to support (e.g., .NE...
