The Windows Software Development Kit for Windows 8 (Windows SDK) contains headers, libraries, and a selection of tools that you can use when you create apps that run on Windows operating systems. You can use the Windows SDK, along with your chosen development environment, to write Windows Store apps (only on Windows 8) using web technologies (such as HTML5, CSS3, and JavaScript), native (C++), and managed (C#, Visual Basic) code; desktop applications that use the native (Win32/COM) programming model; or desktop applications that use the managed (.NET Framework) programming model.
The Windows SDK also includes the Windows App Certification Kit (ACK) to test your app for the Windows 8 Certification Program and the Windows 7 Logo Program. If you also want to test your app on Windows RT, use the Windows App Certification Kit for Windows RT.
The Windows SDK no longer ships with a complete command-line build environment. You must install a compiler and build environment separately. If you require a complete development environment that includes compilers and a build environment, you can download Visual Studio 2012 Express, which includes the appropriate components of the Windows SDK.
For access to additional resources and information, go to the Windows Dev Center.
Version: Windows SDK for Windows 8
Windows ACK Version: 2.2
Date published: November 15, 2012
File name: sdksetup.exe
Updated or Removed Features
The following items were either changed or removed from this version of the Windows SDK.
Tools Many obsolete or deprecated tools have been removed from the Windows SDK. The following tools have been removed:
Apatch.exe, Bind.exe, Checkv4.exe, Consume.exe, DeviceSimulatorForWindowsSideShow.msi, Err.exe, FDBrowser.exe, FXCopSetup.exe, Guidgen.exe, Make-Shell.exe, MDbg.exe, Mpatch.exe, MSIZap.exe, PTConform.exe, ReBase.exe, sddlgen.exe, setenv.cmd, SetReg.exe, SoapSuds.exe, Sporder.exe, TcpAnalyzer.exe, TSPDesigner.exe, UTL2IDL.exe, ValidateSD.exe, VirtualLightSensor.exe, WinDiff.exe, WpfPerf.exe
Supported Architectures:
The Windows SDK for Windows 8 supports building applications for the following architectures:
Note: The Windows SDK for Windows 8 cannot be installed directly on the ARM architecture. You can install the Windows SDK on an x86 or x64 platform, in order to build applications that target the ARM architecture.
Supported Operating Systems:
The installation of the Windows SDK is supported on the following operating systems:
The Windows SDK can be used to build applications that target the following operating systems:
Prerequisites:
In order to install the .NET Framework 4.5 Software Development Kit feature, the .NET Framework 4.5 redistributable package must be installed before the Windows SDK is installed. This release of the Windows SDK does not include a .NET Framework Redistributable Package. You can download the redistributable package from Microsoft Download Center.
To optimize your Windows SDK setup experience, we strongly recommend that you install the latest updates and patches from Microsoft Update before you begin installing the Windows SDK.
Windows SDK Disk Space Requirements
The complete installation of the Windows SDK requires 10 megabytes (MB) to 1 gigabytes (GB) hard disk space for installation, depending on the features selected. Please verify that the computer you are installing to has the minimum required disk space before beginning setup. If the minimum required disk space is not available, setup will return a fatal error.
How to Uninstall SDK Components
When you uninstall the SDK through Programs and Features, most of the SDK components will be uninstalled automatically. However, a few shared components installed by the SDK may need to be uninstalled separately. This guide provides instructions for uninstalling those shared components.
Note: If you uninstall components that other applications use, they will be adversely affected. For example, Visual Studio 2012 also uses the .NET Framework 4.5 SDK.
To uninstall shared SDK components:
This release has the following known issues:
AppVerifier
AppVerifier, a tool for testing and verifying the correctness of running applications, might be installed in such a way that it cannot be separately uninstalled. In order to remove it from your computer, uninstall the App Certification Kit or uninstall the Windows SDK.
.NET Framework 4.5 SDK Tools on Windows Vista and Windows Server 2008
The installer for the Windows SDK for Windows 8 is not supported on Windows Vista and Windows 2008 Server. However, if you have another computer with a supported operating system, you can install the .NET Framework 4.5 SDK Tools on Windows 2008 Server by following these steps.
You can copy these files to a Windows Vista or Windows 2008 Server computer within your organization. These files need to be copied to same directory on the Windows Vista or Windows 2008 Server computer.
Note: Do not redistribute these files outside your organization or as part of any other installer.
Install .NET Framework 4.5 SDK tools by using the command line:
Msiexec /i sdk_tools4.msi VSEXTUI=1
Signtool
Certain operations may fail if you use the x64 version of signtool that is included in the SDK. Please use the x86 version of signtool available under <SDK install location>\Windows Kits\8.0\bin\x86 for all your code signing needs.
WinRT MetaData APIs
If you want to use the WinRT metadata functions, you must install the .NET Framework SDK 4.5 to have access to the complete set of necessary header files. The WinRT metadata functions are RoGetMetadataFile, RoParseTypeName, and RoResolveNamespace in RoMetadataResolution.h. Also, you need the IMetaDataDispenser definition in RoMetadataApi.h and MetaDataGetDispenser in RoMetadata.h.
Windows App Certification Kit Port Usage
The Windows App Certification Kit (ACK) installs a number of services to your machine. One of the services is Te.Service, which allows ACK to perform automated tasks in a secure manner, for example, in the context of a standard user. It also enables other functionality, for example, remote task execution across machines. The service only starts when needed during execution and stops once it is done. When the service starts, it opens firewall ports and doesn’t prompt the user for consent. Though ACK does stop the service and closes the port upon completion.