NtQueryInformationProcess can not be generated

[NeverMorewd]

Actual behavior

NtQueryInformationProcess was not generated.

Expected behavior

NtQueryInformationProcess can be generated after being added to NativeMethods.txt

Repro steps

1. NativeMethods.txt content:

NtQueryInformationProcess
PROCESS_BASIC_INFORMATION

2. NativeMethods.json content (if present):

3. Any of your own code that should be shared?

Context

• CsWin32 version: [0.3.106]
• Win32Metadata version (if explicitly set by project):
• Target Framework: [net6.0;net8.0;netframework48]
• LangVersion (if explicitly set by project): [12]

[Ephron-WL]

I see this generated under Windows.Wdk.PInvoke.NtQueryInformationProcess using Microsoft.Windows.WDK.Win32Metadata 0.11.4. The function is in the Microsoft.Windows.SDK.Win32Metadata as well, but I see it generated from the WDK. You shouldn't have to include the structure, in your native methods files since it will be automatically generated.

[NeverMorewd]

I see this generated under Windows.Wdk.PInvoke.NtQueryInformationProcess using Microsoft.Windows.WDK.Win32Metadata 0.11.4. The function is in the Microsoft.Windows.SDK.Win32Metadata as well, but I see it generated from the WDK. You shouldn't have to include the structure, in your native methods files since it will be automatically generated.

Thank you.I see, some functions were generated from Microsoft.Windows.WDK.Win32Metadata which can be accessed by Windows.WDK.PInvoke not Windows.Win32.PInvoke.

Could I consider all functions from 'ntdll' are declared in namespace 'Windows.WDK'?

[Ephron-WL]

I think it is generally the case, but I wouldn’t guarantee it. Namespaces (courtesy ILSpy): ***@***.*** From: Easley wang ***@***.***> Sent: Tuesday, September 24, 2024 8:12 PM To: microsoft/CsWin32 ***@***.***> Cc: William Lucking ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/CsWin32] NtQueryInformationProcess can not be generated (Issue #1282) I see this generated under Windows.Wdk.PInvoke.NtQueryInformationProcess using Microsoft.Windows.WDK.Win32Metadata 0.11.4. The function is in the Microsoft.Windows.SDK.Win32Metadata as well, but I see it generated from the WDK. You shouldn't have to include the structure, in your native methods files since it will be automatically generated. Thank you.I see, some functions were generated from Microsoft.Windows.WDK.Win32Metadata which can be accessed by Windows.WDK.PInvoke not Windows.win32.PInvoke. Could I consider all functions from 'ntdll' are declared in namespace 'Windows.WDK'? — Reply to this email directly, view it on GitHub<#1282 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKMJDOKAVNM3VENWXNWZMI3ZYISY5AVCNFSM6AAAAABOCGAH36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZSHAYTOMZTG4>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[NeverMorewd]

Got it, thank you!