I've used VS2008 on my development machine for some years now, with windows SDK v7.1. I've installed VS2010, and it's using the Windows SDK v7.0a, but I need it to use the Windows 7.1 SDK (which I had installed prior to installing VS2010). When I run the Windows SDK 7.1 configuration tool, to switch the Windows SDK in use, the tool updates for VS2008, but not for VS2010. The message it reports is: 'The Windows SDK Configuration Tool has successfully set Windows SDK version v7.1 as the current version for Visual Studio 2008' The configuration tool is installed with the Windows 7.1 SDK and is found here: 'C: Program Files Microsoft SDKs Windows v7.1 Setup WindowsSdkVer.exe' VS2010 continues to use WSDK 7.0a, which extremely frustrating, as I need to do DirectShow development (so I need to build the baseclasses, which aren't released with 7.0a release of WSDK). Would I be correct in assuming that it's not updating VS2010 settings because VS2010 wasn't installed at the time that I installed Windows 7.1 SDK? Can I fix this manually, or should I uninstall Windows 7.1 SDK, then reinstall it? Any other suggestions / workarounds for this?
If you install the 'Windows XP Support' option in Visual Studio 2012 or later, then you already.have. the Windows 7.1A headers & libraries. They are used by the ``v1??xp`` Platform Toolset option. Known issue: The Windows 7.1 SDK installer has the same conflict issue with the updated Visual Studio 2010 REDIST files as the release.
See for details. Known issue: If you try to install the Windows 7.1 SDK on a system with VS 2012 Update 1 or later, VS 2013, or VS 2015 it will likely fail. This I because these versions of Visual Studio already included a trimmed down Windows 7.1A SDK to support the ' Platform Toolset. The Windows 7.1A SDK does not include samples, so if you are trying to get those legacy samples you should set up a fresh machine or VM to install the original standalone Windows 7.1 SDK, then copy out the desired files. Windows SDK for Windows 7 and.NET Framework 4.0 (v7.1) is now available.
It includes a free command-line version of the Visual C 2010 compiler including support for /analyze static code analysis. This release of the Windows SDK supports Windows 7, Windows Server 2008 R2, Windows Server 2008, Windows XP SP3, Windows Vista, and Windows Server 2003 R2 using Visual Studio 2005, 2008, or 2010. Note that the relies on the Windows SDK platform headers and libraries that shipped with the Visual Studio 2008 (Windows SDK 6.0A) or later. The WindowsTouch sample requires Windows SDK 7.0 or later to compile. Stock Trade Manager 3.01.
This version is slightly newer than the Windows SDK that ships with VS 2010 itself (Windows SDK 7.0A). For VS 2005 and VS 2008, integrating Windows SDK 7.1 works the same way as it had previously updating the global settings. Be sure to reference the DirectX SDK include and lib paths before the Windows SDK to ensure proper search order. For Visual Studio 2010, the Windows SDK 7.1 creates new platform targets for its headers which have to be selected on a project basis under the setting Platform Toolset. This value defaults to v100 which is the VS 2010 compiler toolset and the Windows SDK 7.0A.
Install Windows Sdk 7.1 On Windows 10
With the Windows SDK 7.1, you get a new option Windows7.1SDK which uses the VS 2010 compiler toolset that ships in the Windows SDK along with the updated headers and libraries. If you have Visual Studio 2008 installed, you will also be able to select v90 which is the VS 2008 compiler toolset and the Windows SDK 6.0A. The v90 is required for Managed C.NET 2.0 development since the VS 2010 toolset only supports.NET 4.0 development. We also use this technique with the DirectX SDK Content Exporter sample in the June 2010 release because the version of the library we use for that sample does not include VS 2010 libraries, and therefore we have to use the VS 2008 toolset to ensure we are using the VS 2008 C Runtime. The DirectX SDK (June 2010) does not create its own Platform Toolset because it does not include a C compiler like the Windows SDK does.
Instead, we explictly add VC Directory settings to each VS 2010 project that include the DX SDK path references using the $(DXSDKDIR) variable. The Windows 7.1 SDK includes the headers for Direct3D 9, Direct3D 10, Direct3D 11, DirectSound, DirectInput, DirectMusic 'core' APIs, and XInput 9.1.0. The d3dcommon.h is slightly outdated compared to the version in the Windows 8.0 SDK and the DirectX SDK (June 2010), so the newer defines like D3DPRIMITIVETOPOLOGY, D3DPRIMITIVE, D3DSRVDIMENSION, etc. Are not defined for the Windows 7.1 SDK version.
You'll need to use D3D10 or D3D11 versions instead. Update: The Windows 7.1 SDK provides the VS 2010 RTM compiler, and can overwrite VS 2010 Service Pack 1 files if installed on the system. See for a fix.
1 VS 2010 comes with Windows SDK 7.0A, not 7.1. If you still need to support Windows 2000, I suggest you to use Windows SDK 6.0A. 2 windows.h isn't for C# applications. If you need help in using the function via.Net interop technologies, try the CLR forum under the.Net development category. The following is signature, not part of post Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem. Visual C MVP. Hi Sheng, Thanks for reply.
Thanks for clarification regarding Windows SDK installed with VS2010. To clarify things, I'm translating C application to C#. The 'Windows.h' problem is in fact when I try to compile my original C application using VS2008. That same C application could compile without problem before. My problems began in fact, I think, after I uninstalled 'Visual Studio Tools for Applications 2.0' which got installed while installing SQL Server 2008 R2. Following your post, I just modified the corresponding commands. As an example: In C this-IMGLogoPPeint-Image = Bitmap::FromResource((System::IntPtr)GetModuleHandle(0), 'IDBLOGOVISU'); to this-IMGLogoPPeint-Image = Bitmap::FromResource((System::IntPtr)(Marshal::GetHINSTANCE(Assembly::GetExecutingAssembly-GetModules0)), 'IDBLOGOVISU'); In C# this.IMGLogoPPeint.Image = Bitmap.FromResource((System.IntPtr)GetModuleHandle(0), 'IDBLOGOVISU'); to this.IMGLogoPPeint.Image = Bitmap.FromResource((System.IntPtr)(Marshal.GetHINSTANCE(Assembly.GetExecutingAssembly.GetModules0)), 'IDBLOGOVISU'); In C#, everything compile without problem.
In C, I now have this error: 1Project: error PRJ0003: Error spawning 'resgen.exe'. Can you help? There isn't an option to add/remove SDK 6.0A from the VS2008 setup. Yes, those keys could be left over when you uninstall VS2008. You probably want to repair SDK 7.0 after VS 2008 install.
VS 2008 plugins need to be reinstalled too, You may still want to use the VS9 toolset when needed, VC2010's compiler can only support.Net 4.0 VS2010 targets XP SP2 or higher. SP3 or higher if you use.Net 4.0 If you do not want VS2008, you can install an earlier version of SDK, like platform SDK feb 2003 fpr Windows 2000 development. The following is signature, not part of post Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
Visual C MVP. It depends on which tool do you need or which platform you want to support. For example mscorcfg.msc is shipped with.Net 2.0 SDK (and VS 2005) and Windows SDK for Vista but not in later SDK versions. And the signwizard switch of signtool.exe got removed from Windows 7 SDK. And the 6.0A SDK is the last SDK that supports targeting Windows 2000. The following is signature, not part of post Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem. Visual C MVP.