Description
Currently when detecting Windows 10 SDKs we look for a registry key and then assign a generic '10.0' SDK with some [info](
https://github.com/appcelerator/windowslib/blob/3cc8f1aa20c4ba6eb4c65ffca520e7cf4e7d4e55/lib/windowsphone.js#L138-L171)
We can improve the individual SDK detection by following a similar method to one of the utility scripts called by VsDevCmd,
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\vsdevcmd\core\winsdk.bat
That files basic flow when searching for an SDK is
is one of HKCU\SOFTWARE\Wow6432Node, HKLM\SOFTWARE, or HKCU\SOFTWARE
Get the installation folder using {{reg query \Microsoft\Microsoft SDKs\Windows\v10.0 /v "InstallationFolder"}
Set to WindowsSdkDir
For each directory in <WindowsSdkDir>\include\
- Look for <WindowsSdkDir>\include\<version>\um\Windows.h, if it exists it's a valid SDK
I'm not sure what changes would be required to the SDK build process if we switched from using an generic 10.0 to individual SDKs
We already do this [https://github.com/appcelerator/windowslib/blob/3cc8f1aa20c4ba6eb4c65ffca520e7cf4e7d4e55/lib/windowsphone.js#L173-L181] but due to TIMOB-24958 I think we might need to expand upon this more and split the SDKs an underlying info out a bit more
Can we close this since we have resolved TIMOB-24958?
I think this can be closed for now because we already have this feature. Feel free to reopen if that's not the case.