[Question] Why does 5.0 drop support for .net standard 2.0

[sensslen]

I'm currently developing an application that also needs to support .net framework. I started by using version 4.x and it was working very well. However I cannot update to 5.0 because of dropped support for .net standard 2.0. Is there a compelling reason to drop netstandard support? If so I probably will have to look for alternatives.....

[natemcmaster]

I dropped it because .NET Framework is increasingly feeling like Microsoft is abandoning this in favor of the unified .NET 5+ target frameworks. It was getting harder to keep the project cross-compiling for it. For example, as I tried to take advantage of new C# language features like nullable annotations and source generators, I found .net standard and .net framework didn't compile without hundreds of conditional compilation statements.

Are there specific features you're wanting in 5.0?

[sensslen]

I was looking for #553 mainly - but generally want to keep my nuget dependencies up to date...

[natemcmaster]

I would be okay to cherry-pick #553 on top of 4.1 and release a patch.

And if someone wants to try to get the main branch to compile for net48 directly, I'll reconsider. I don't have a way to know how many people are using .NET Framework - not sure nuget makes those metrics public - but if there is a way, I'd also like to know if this is causing wider spread issues.

[gududege]

Please support net48.

[sensslen]

I created #591 which allows multi targeting.

@natemcmaster @gududege please feel free to jump in with suggestions.

[natemcmaster]

Thanks for the contribution. Released as https://github.com/natemcmaster/CommandLineUtils/releases/tag/v5.0.1