Integrating Windows SDK and VS with new SDK Configuration tool

re: Integrating Windows SDK and VS with new SDK Configuration tool

Larry — Sun, 11 Dec 2011 13:59:24 GMT

Is there something like this tool for VS2010 and SDK 7.1? If run the cl.exe from the SDK command prompt (with /showIncludes) it uses the headers from the 7.1 SDK. But Visual Studio 2010 SP1 still uses the 7.0A headers.

Windows SDK for Windows 7 and .NET Framework 3.5 SP1 の詳細

とっちゃん's Blog — Wed, 04 Feb 2009 07:29:38 GMT

Windows SDK for Windows 7 and .NET Framework 3.5 SP1 の詳細

Released: Windows SDK for Windows 7 and .NET Framework 3.5 SP1: Beta

Microsoft Windows SDK Blog — Tue, 03 Feb 2009 04:26:25 GMT

The Windows SDK for Windows 7 and .NET Framework 3.5 SP1: Beta has been released (ISO-format). As many

Some new post-mix downloads

Just Code - Tamir Khason — Thu, 01 Jan 2009 22:01:20 GMT

[This blog was migrated. You will not be able to comment here. The new URL of this post is http://khason

Where is UISpy.exe?

Microsoft Windows SDK Blog — Thu, 13 Nov 2008 05:25:29 GMT

The UI Spy tool did not ship in the Windows SDK for Windows Server 2008 and .NET Framework 3.5 , released

How to get the WinSDK Configuration Tool to work

Microsoft Windows SDK Blog — Mon, 06 Oct 2008 22:12:37 GMT

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you

How to get the SDK Configuration Tool to work

ascend slowly, breathing normally — Mon, 22 Sep 2008 02:46:02 GMT

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you

WinSDK bug notification: SDK Config Tool appears to work but fails

Microsoft Windows SDK Blog — Tue, 01 Jul 2008 01:23:51 GMT

This article applies to the Windows SDK for Windows Server 2008 and .NET Framework 3.5 , when used with

re: Integrating Windows SDK and VS with new SDK Configuration tool

Brian Cost — Thu, 15 May 2008 00:25:18 GMT

JDalal, I've sent you an email with a few questions. We're researching this issue and trying to repro it now. There is a known issue with the SDK Configuration Tool with XP, with a workaround posted here: http://blogs.msdn.com/windowssdk/archive/2008/03/07/workaround-sdk-build-env-fails-on-x86-xp-with-vs2005.aspx

Karin Meier

Windows SDK Team

re: Integrating Windows SDK and VS with new SDK Configuration tool

JDalal — Sun, 11 May 2008 00:36:59 GMT

Ok I think I found the fix. I think, the sdk configuration tool modifies the HKLM value. But for some reason if the corresponding HKCU value was set, the VS2008 picks that value up and before reading the HKLM value. VS command line correctly looks at the HKLM value (I guess it reads from vcvars32.bat).

I just modified HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder to point to v6.1 install folder and VS picked it up.