I noticed that as of v1.4.0 support for .NET 4.5 Framework has been dropped in favor of .NET 6. This has also been mentioned on issue #804, and the accepted solution was the fact that .NET 4.8 is supported through the netstandard2.0 target.
However, when it comes to older frameworks such as .NET 4.6.1/4.6.2, even though they do support .NET Standard 2.0, when compiling a project that references netstandard libraries, it generates an additional 96 assemblies it the build output, which is quite annoying.
Because of that, many nuget packages also provide a net461 or net462 target, that allows them to be referenced without producing those additional assemblies. No code changes are required, since all the NETStandard APIs are present in those frameworks.
Therefore I would like to request that framework to be included as a build target in this project. Since .NET 4.6.1 has recently come to end of support, maybe you could add net462 as a target to this library.
Hello,
I noticed that as of v1.4.0 support for .NET 4.5 Framework has been dropped in favor of .NET 6. This has also been mentioned on issue #804, and the accepted solution was the fact that .NET 4.8 is supported through the
netstandard2.0target.However, when it comes to older frameworks such as .NET 4.6.1/4.6.2, even though they do support .NET Standard 2.0, when compiling a project that references netstandard libraries, it generates an additional 96 assemblies it the build output, which is quite annoying.
Because of that, many nuget packages also provide a
net461ornet462target, that allows them to be referenced without producing those additional assemblies. No code changes are required, since all the NETStandard APIs are present in those frameworks.Therefore I would like to request that framework to be included as a build target in this project. Since .NET 4.6.1 has recently come to end of support, maybe you could add
net462as a target to this library.Anyway, thanks for your attention.