Visual Studio 2013 RTM is now available. The VS 2013 RTM Redistribution packages are also available (x86, x64, ARM), as well as the Remote Debugging Tools (x86, x64, ARM). For more information, see the Visual C++ team blog, Somasegar’s blog, and the Visual Studio team blog.
VS 2013 RTM includes the Windows Software Development Kit (SDK) for Windows 8.1 (October 2013), which is also available standalone. This includes DirectXMath 3.06, Direct3D 11.2/DXGI 1.3/Direct2D 1.2/DirectWrite 1.2 headers for Windows 8.1, D3DCompiler #47, and the Direct3D Debug Runtime for Windows 8.1. This includes an update of GDFMaker with some minor bugs fixes, and a few more caps detection features in DxCapsViewer as well.
Windows XP developers: as with VS 2012, the “v120_xp” platform toolset in VS 2013 uses a version of the Windows 7.1 SDK, not Windows 8.x SDK. See Visual Studio 2012 Update 1.
Windows 7 users: VS 2013 originally required IE10 be installed which requires KB 2670838 (DirectX 11.1 and Windows 7 Update and DirectX 11.1 and Windows 7). The VS 2013 setup has been refreshed and no longer requires IE10 be installed. KB 2670838 and IE10 are still recommended as there are a number of known issues on Windows 7 if they are not present (see KB 2906882) some of which are addressed with VS 2013 Update 1.
Windows 8 users: If you upgrade to Windows 8.1, remember that all attempts to use
D3Dxx_CREATE_DEVICE_DEBUG will fail until you upgrade the Developer Runtime. You can do this by installing VS 2013, the standalone Windows 8.1 SDK, or by installing the VS 2013 Remote Debugging Tools. If you are missing the updated SDK Debug Layers, you should see the following message in your debug output:
D3D11CreateDevice: Flags (0x2) were specified which require the D3D11 SDK Layers for Windows 8.1, but they are not present on the system.
These flags must be removed, or the Windows 8.1 SDK must be installed.
DirectX SDK users: Using the legacy DirectX SDK (June 2010) with VS 2013 is the same as it was using it with VS 2012. See MSDN.
Express users: VS 2013 Express for Windows edition include Graphics Diagnostics (aka VS PIX) and the Visual Studio content tools. These are not included with the VS 2013 Express for Windows Desktop edition.
VS 2010/2012 users: You can use the property sheet technique for the Windows 8.1 SDK that was described in this Visual C++ Team blog post originally for VS 2010+Windows 8.0 SDK. For VS 2010, just change the part of the paths with “8.0”/”win8″ to “8.1”/”winv6.3″ but otherwise use all those instructions. For VS 2012, you can simplify all the paths to just add the 8.1 paths before the existing value for each variable. The updated .props are attached to this blog post. This should only be used for Win32 desktop application development. Windows Store apps should use VS 2013 with the Windows 8.1 SDK. Note you cannot target Windows XP with the Windows 8.1 SDK.
The VS team’s instructions omit including the “include\winrt” directory under the assumption that those are for Windows Store apps only, but that’s not strictly true. At a minimum, having access to #include <wrl/client.h> provides you the extremely useful Microsoft::WRL::ComPtr smart-pointer that works perfectly fine in Win32 desktop apps and down-level systems.
Windows Store app developers: Remember if writing Windows Store apps for Windows 8.1, you must use the VS 2013 toolset, the Windows 8.1 SDK, and the Windows 8.1 OS. You can optionally install the VS 2012 toolset and Windows 8.0 SDK as part of your VS 2013 setup (called “Tools for Maintaining Store apps for Windows 8” in the optional features list) to maintain Windows Store apps for Windows 8.0. You cannot install VS 2013 on the Windows 8.0 OS to build Windows Store apps for Windows 8.1. None of these restrictions apply to Win32 desktop development.
Update: Refreshed the attached .props with some fixes on October 21, 2013. There are new releases of DirectXTex, DirectXTK, Effects 11, and DXUT for Direct3D 11 with support for VS 2013 / Windows 8.1 SDK available as well.