Announcement: DirectX SDK (June 2010) is live

The June 2010 release of the DirectX SDK is now available on Microsoft Downloads. This release introduces official support for Visual Studio 2010, an updated version of the HLSL compiler with numerous fixes and minor improvements, improved documentation and samples, XNAMath C++ SIMD library version 2.03, and PIX for Windows usability improvements.

For download details, see the DirectX Developer Center and What’s New and Release Notes for June 2010.

The updated DirectX SDK documentation and Windows DirectX Graphics documentation are both currently posted to MSDN.

The corresponding DirectX End-User Runtime with the June 2010 updated DLLs for D3DX9/10/11, D3DCSX, D3DCompiler, XAUDIO2, and XACT is also available online (Web or stand-alone).

Update: Please note that the REDIST folder for the DirectX SDK (June 2010) is slightly out of date now. You should make use of the refreshed version of DirectSetup if you need the REDIST.

Known Issues: Be sure to read this article for known issues trying to install the DirectX SDK (June 2010) due to a problem with the Visual Studio 2010 CRT.

Note: The DirectX SDK is now legacy. You should use the Windows 8.1 SDK instead, or at least prefer the Windows 8.1 SDK over the legacy DirectX SDK as much as possible.

Related: DirectX SDKs of a certain age, The Zombie DirectX SDK, Living without D3DX, DirectX SDK Tools Catalog, and DirectX SDK Samples Catalog

Comments (4)

  1. Steve Scott says:

    Does the VS 2010 support mean that the text rendering improvements in WPF4 (from here…/wpf-text-clarity-improvements.aspx ) are, or will be, ported across so non-WPF Direct2d apps can benefit?

  2. The DirectX components (Direct3D, Direct2D, DirectWrite, DirectInput, DirectSound, DirectShow, DirectMusic, etc.) are shipped as part of the OS. As of Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1, they are never updated by the DirectX SDK or the DirectX End-User Runtime.

    Direct2D improvements or updates would therefore only be released via Windows Update or a Service Pack, not as part of the DirectX SDK.

    That said, I believe the issue you refer to is actually something about the way rendering was done by WPF, not an issue with Direct2D itself.

  3. dsBL10 says:

    – what are the differences between the JUNE2010 SDK version and the one integrated into Windows 7.1 SDK ?

    – which version shall be used/prefered for new developments ?

  4. RE: dsBL10

    The Windows 7.1 SDK has essentially the same headers for Direct3D 11, Direct3D 10.1, DXGI, DIrect3D 9, Direct2D, DirectWrite, DirectSound, and DirectInput. There are some differences as many of the shared types for D3D10 and D3D11 were moved into d3dcommon.h, but it should compile with the same types.

    The Windows SDK 7.1 will not provide D3DX, the HLSL compiler, the debug layer, XAUDIO2, XACT, XNAMath, DXERR, PIX for Windows, or many of the samples.

    If you using the Windows SDK 7.1 xinput.h, you will get a very dated version of XINPUT that does not support the wireless dongle and devices. The DirectX SDK xinput.h is for the latest XINPUT 1.3.