I have had the pleasure of contributing to a couple different networked drivers with very talented maintainers that I like to use as references. One supports a

I have had the pleasure of contributing to a couple different networked drivers with very talented maintainers that I like to use as references. One supports a wide array of Framework versions and has both Sync and Async I/O, as it must to implement the ADO.NET database driver interfaces. Reading the internals really highlight the way that .NET has evolved over the years and what must be done in each target version to maximize performance: https://github.com/mysql-net/MySqlConnector https://github.com/mysql-net/MySqlConnector The other supports .NET 6 only with Async I/O only. This support policy seems to be the way that "modern" .NET development is headed, as .NET 6 will be the floor for LTS .NET (formerly .NET Core) releases in a few months. Async APIs only greatly simplify development, and make it simpler to remain performant when targeting WASM. https://github.com/Cysharp/AlterNats https://github.com/Cysharp/AlterNats As a library maintainer, one thing I often wonder about is how to indicate .NET version support. One option would be for the major version of the library to track the major version of .NET, so if I were to publish a new library today then start with .NET 6 support and start with version number 6.0.0 instead of 1.0.0. This would limit the library to only making breaking changes when the .NET version changes though.