DirectoryServices deployement on nano serve Unable to load activeds.dll

[winsquall]

Hello,

I try to deploy a .netcore 2 app on a docker nanoserver. This app is using Mirosoft.DirectoryServices and i always have an error "Unable to load activeds.dll. Module not found..." when it try to use it.
I try to put the dll into the container in c:/windows/system32 but nothing change.

Can somebody help me about this issue?

Regards.

[danmoseley]

@tquerec, @josephisenhour, @bongiovimatthew-microsoft can you confirm whether System.DirectoryServices is expected to work on Nano?

My assumption is not - I believe activeds.dll is not part of WCP ?

[josephisenhour]

That's correct, System.DirectoryServices doesn't work with nano yet.

[danmoseley]

@josephisenhour "yet" .. is it planned? maybe that's the same question as, do you expect to put activeds.dll in the image.

Either way it would be nice to have a more specific message.

[josephisenhour]

It is planned and some work is underway, but there are no specific dates yet.

[winsquall]

Many thanks @danmosemsft , @josephisenhour .
Until a new image of nanoserver is release, is there a workaround more efficient than put the activeds.dll in system32?
Regards

[ViktorHofer]

@tquerec, @josephisenhour, @bongiovimatthew-microsoft does System.DirectoryServices now work on Windows 10 Nano? Please triage this and set a milestone.

[LisavB]

Is there currently a suggested workaround for this issue? And is the date this issue will be fixed known?

[danmoseley]

@tquerec do you know?

[tquerec]

There is no reasonable workaround I know of. There was work to move ADSI into the onecore package but this does not necessarily mean it's also included in nano. The best way to figure this out may be to install the latest nano package and look for the presence of any of the ADSI binaries ( activeds.dll, etc ).

[LisavB]

Thanks @tquerec, the activeds.dll package wasn't present for me in the nano server package.
Is there planned work to add these to the nano-server?

In case anyone else is stuck, using System.DirectoryServices.Protocols to use LDAP to access AD directly are working for me as a workaround.

[af-mst]

Are there any updates on this topic since Jul 2018?
We would really appreciate using nano, because if the considerably lower size compared to core (which we currently use)

Regards