Porting to .netstandard 2.0+

MichaelGrafnetter / DSInternals

Directory Services Internals (DSInternals) PowerShell Module and Framework

https://www.dsinternals.com

MIT License

1.65k stars 254 forks source link

Porting to .netstandard 2.0+ #68

Open sumantfordev opened 5 years ago

MichaelGrafnetter commented 5 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 3 years ago

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

MichaelGrafnetter commented 3 years ago

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

derSchweiger commented 3 years ago

Great news, thank you very much!

Friedricj commented 3 years ago

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