Along with global launch of Windows 10 build 10240 (RTM), Microsoft opened the path for the developers to build and publish apps for Windows 10. The Software Development Kit (SDK) is available for download. This SDK for Windows 10 contains headers, libraries and tools you can use to build apps.
In this post, sharing/bookmarking the link to download the SDK Tools for Windows 10 along with the known issues currently there in this build.
If you didn’t yet upgraded to the Windows 10 build, you can follow this post to download the ISO image or upgrade directly from Windows 7 or Windows 8.x systems. You also need Visual Studio 2015 to develop apps for Windows 10. You can download Visual Studio 2015 (ISO + Web Installer are included) from Microsoft by visiting the post.
You can also go for a Community Edition of the Visual Studio 2015, which is free for individual developers, open source development, academic research, education and small professional teams to build cross-platform mobile apps for Windows, iOS and Android. You can download it from here: Visual Studio 2015 Community Edition (Free).
Please note that, this SDK also supports building Windows apps and desktop applications for Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008 R2 and Windows Server 2008. Also, you don’t need to install this SDK if you are using Visual Studio 2015. This SDK is already included. If you installed Visual Studio 2015 prior to Windows 10 launch, you need to rerun the setup to install the SDK for Windows 10.
- Windows SDK Version in Setup and Control Panel does not match the version on disk. The UI will show version 10.0.26627.0 rather than 10.0.10264.0.
- You might not be able to uninstall App Verifier, a tool for testing and verifying the correctness of running apps, separately. To remove it from your computer, uninstall the App Certification Kit or uninstall the Windows SDK.
- The tool to do manual testing of UI automation, does not run on ARM devices in Windows 10.
- Windows Performance app will crash when expanding memory graphs in Graph Explorer, due to a known issue with Resident Set Memory graph. As a work around, avoid capturing resident set information in the trace.
- When a device is in the developer unlocked state and a side-loaded application has the debuggable capability, any crash dumps for that application will be redirected to the user documents folder of the device for local debugging and the crash will not be sent to Microsoft for analysis.