How to know which Windows SDK APIs are being used?

[stevenbrix]

Hey, I wasn't able to find an answer when looking through other discussions/docs, so I figured I'd ask here.

I'm wondering about the versioning scheme of the Microsoft.Windows.SDK.Win32Metadata package. The early versions matched the Windows SDK version that the metadata was for. This made it easy to understand which version of the SDK you were pulling in. But now, the packages follow a different versioning scheme which isn't as easy to follow.

How do I know which Windows SDK headers are being used?

@riverar @mikebattista I would appreciate some insight here!

[mikebattista]

You should assume the latest SDK with some lag between new SDK releases and metadata updates. If there's ever an API in a new SDK that you need that's missing from the metadata, please file a bug to encourage us to update. Usually, updating the SDK is pretty trivial, but we hit a snag with the most recent SDK (#1930), so we are still behind on that one.

If you want to know specifically which SDK is used, you can see the dependency below. Switch to whatever release tag you're interested in to see what the dependency was at the time that metadata package was published.

win32metadata/BuildTools/BuildTools.proj

Lines 11 to 12 in c2b7ea9

	<PackageReference Include="Microsoft.Windows.SDK.CPP" Version="10.0.22621.2428" GeneratePathProperty="true"/>
	<PackageReference Include="Microsoft.Windows.SDK.CPP.x64" Version="10.0.22621.2428" GeneratePathProperty="true"/>