We used to make libraries that target .NET Standard 2.1 and .NET Framework 4.8 as minimum requirements since most of our libraries came from the source code of Kernel Simulator.
Over time, new libraries get released, targeting the .NET Standard 2.0 framework to provide support for the widest range of .NET versions possible.
Unfortunately, one of the libraries got warnings from the building system that stated that the Extensification .NET Framework version was in use instead of the targeted version.
As a result, we made a plan to remove this warning by re-targeting all our libraries to .NET Standard 2.0. The following libraries are affected: (Names from their parts)
- TermRead (netstandard2.1;net4.8)
- GRILO.Boot (netstandard2.1;net4.8)
- ShoutStats.Core (net6.0;net5.0;net4.8)
- VT.NET (netstandard2.1;net4.8)
- Namer (netstandard2.1;net4.8)
- VisualCard (net6.0;net4.8)
- NameNumerizer (net6.0;net5.0;net4.8)
- ManagedWeatherMap (netstandard2.1;net4.8)
- Dictify (netstandard2.1;net4.8)
- Addresstigator (net6.0;net5.0;net4.8)
As a result, the warnings are removed when building the affected libraries. There is only one library to which we can’t apply this change: LineNumbers.Core. It uses Microsoft.Build to process the Visual Studio solution and project files.
As a result, libraries that target .NET Standard 2.0 now no longer see the warning after upgrading the abovementioned libraries.
Now, you may ask why. The reason is that we want to prioritize compatibility over feature parity for libraries.
Enjoy coding!
Aptivi 
Thoughts?