There should be a switch to exclude SDK/WDK from consideration

I am working with Windows Filtering Platform APIs. They are available both for user-level applications and drivers thus there are 2 separate declarations in windows metadata. So when I try to generate some API, let's say FwpmEngineOpen0, I get an error: The API "FwpmEngineOpen0" is ambiguous. Please specify one of: or "Windows.Wdk.NetworkManagement.WindowsFilteringPlatform.FwpmEngineOpen0" or "Windows.Win32.NetworkManagement.WindowsFilteringPlatform.FwpmEngineOpen0". So I have to specify the full name Windows.Win32.NetworkManagement.WindowsFilteringPlatform.FwpmEngineOpen0. Same thing pretty much for every WFP API. At the same time we can assume most users are working for user-level apps and not drivers in C#. So I think, there should be a flag in project file to exclude either WDK or SKD APIs from consideration. So we get:

• By default both SDK and WDK are considered
• User can disable WDK, so APIs will be searched only in SDK
• Wise versa with the previous point

With this setup e.g. in my particular use case I would disable WDK and specify 'simple' names in NativeMethods.txt like just FwpmEngineOpen0 and not get an error

Start by tracing how the project file controls API generation and how names from NativeMethods.txt are resolved against SDK and WDK metadata. Define how the configuration selects SDK, WDK, or both while preserving the current default, then verify that an unqualified name such as FwpmEngineOpen0 resolves without ambiguity when one source is disabled.