Ilya (@iSazonov) The same DLL is used by AssignProcessToJobObjectDllName and QueryInformationJobObjectDllName. Do these also not work on Win7?

If we are replacing them with kernel32.dll, have you verified the change on win7throughwin10`?

If replacing with kernel32.dll works, should we be removing the definitions from PInvokeDllNames.cs.

Aditya Patwardhan (@adityapatwardhan) I removed all links to api-ms-win-core-job-l2-1-0.dll and now it works for me on Windows 7.

should we be removing the definitions from PInvokeDllNames.cs

There is already some unused consts, the list is large and numerated, also we could want to use ApiSets again after Windows 7 EOL. I think we need to keep the consts.

Do we know if things are still working properly on NanoServer and Windows IoT after changing to kernal32.dll?

I can not test on Nano and IoT.
I saw that .Net Core team replaced ApiSets with direct dll names because of many such problems with ApiSets.
See:
dotnet/corefx@75e45da
More: https://github.com/dotnet/corefx/search?q=ApiSets&type=Commits

Also I found https://www.geoffchappell.com/studies/windows/win32/apisetschema/history/sets61.htm where we can see that there is sometimes automapping (for Windows 7).

Windows 7 API Sets

I have verified that the change works on NanoServer 1903 image.

🎉v7.0.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes

Hey, shouldn't we remove the corresponding constants from the PinvokeDllNames class since they are unused now?

Friedrich von Never (@ForNeVeR) We did not remove the constants because we will revert the change after Windows 7 EOL.

Okay, thanks.

🎉v6.2.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes