Porting to .netstandard 2.0+

[sumantfordev]

No description provided.

[MichaelGrafnetter]

To maintain Windows Server 2012 R2 RTM support in the PowerShell module, the target .NET Framework needs to be kept at version 4.5.1, which corresponds to .NET Standard 1.2 AFAIK.
Revamping the project files and multi-targeting NuGet packages is on my TODO list.

[sumantfordev]

why not .net standard 2.0 or 3.0,
As i understand the only limitation of running in windows server versions, that can still be there with .net standard 2.0/3.0

[MichaelGrafnetter]

Gotchas:

• .NET Core 2 is out of question, as it does not support C++/CLI AFAIK. So .NET Core 3+
• .NET Framework's internal classes are used in 2 instances. This can of course be changed.

I am currently working on improving FIDO stuff and better NTDS schema parsing, which takes 100% of my free time. I would therefore welcome any help in porting the project to .NET Core 3.

[derSchweiger]

Support for .NET Core 3+ would be a big deal for me too. Thanks for your great work!

[MichaelGrafnetter]

I already started work on rewriting code that is bound to .NET Framework and build scripts.

[derSchweiger]

Great news, thank you very much!

[Friedricj]

I have created a pull request that would simplify it for us to reference the packages then from a .Net Core 3.1 project.