Microsoft Windows SDK Blog : SDK Config Tool

Development with Windows SDK & DirectX SDK when Visual Studio 2008 is installed

wsdkblog@microsoft.com — Thu, 15 Oct 2009 23:08:00 GMT

In order to utilize DirectX SDK resources you should ensure that the DirectX SDK include, library, and executables directories are set correctly in Visual Studio 2008. The order in which Visual Studio 2008 looks for executable directories and library files is important. The Windows SDK directories should appear above the DirectX SDK directories.

The DirectX SDK includes some files that are also shipped in the Windows SDK. These files may also be installed with the Windows headers and libraries that are included in Visual Studio 2008. It's possible to get a mixture of different versions of DirectX files on your computer, depending on what versions of the Windows SDK, DirectX SDK, and Visual Studio you install.

The Windows SDK Configuration tool can be used set the Windows 7 SDK as the “current” SDK for MSBuild and VCBuild. This will update the Windows 7 SDK build environment and the Visual Studio 2008 build environment to use the Windows 7 SDK headers, libraries and tools. You can also use this tool to switch it back again. However, the configuration tool does not set the DirectX SDK paths. You will need to do this manually, following the instructions in this article.

If you have installed the DirectX SDK and wish to build an application in the Windows SDK command line build environment, or in the Visual Studio build environments, you will need to set the VC++ directory paths manually. If you wish to build with the Windows 7 headers and libraries, you should ensure that directory path for this content is found first, before the DirectX SDK content.

In the following example I have installed the November 2008 version of the Microsoft DirectX SDK on a computer with the Windows 7 SDK and Visual Studio 2008.

How to set the C++ Directories manually

1. Launch Visual Studio 2008.

2. Open the Tools menu and select Options…. The Options dialog box appears.

3. In the left pane of the Options dialog box, expand the Projects and Solutions node.

4. Under Project and Solutions, select VC++ Directories.

5. In the right pane, set the "Platform" drop-down list box to Win32® and the "Show directories for" drop-down list box to "Executable" files.

6. At the bottom of the list of executable file directories, create a new entry for the DirectX SDK: [drive]:\Program Files\Microsoft DirectX SDK [version]\Utilities\bin\x86 (If there is already such an entry, move it to the bottom of the list.)

7. Set the "Show directories for" drop-down list box to "Include" files.

8. At the bottom of the list of directories, create a new entry for the DirectX SDK: [drive]:\Program Files\Microsoft DirectX SDK [version]\Include (If there is already such an entry, move it to the bottom of the list.)

9. Set the "Show directories for" drop-down list box to "Library" files.

10. At the bottom of the list of directories, create a new entry for the DirectX SDK: [drive]:\Program Files\Microsoft DirectX SDK [version]\LibX86 (If there is already such an entry, move it to the bottom of the list.)

11. If you are developing an application to run on AMD64, you should repeat these steps to set the AMD64 paths by setting the "Platform" drop-down list box to X64 and providing the appropriate paths.

12. Click OK.

Karin Meier-Magruder
Program Manager
Windows C++ Team

Send your thoughts to the Windows SDK Feedback alias. Tell us how you use the SDK and what we can do to improve your development experience.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Windows SDK Configuration Tool May Report an Error When OS Display Format is not English

wsdkblog@microsoft.com — Sat, 22 Aug 2009 00:33:00 GMT

This post describes a problem with the Windows SDK Configuration Tool, which is used to set the version of Windows SDK headers, libraries and tools you wish to build with in the Visual Studio or Windows SDK build environments.

Issue: When you launch the Windows SDK Configuration Tool on a system which has Visual Studio 2005 or Visual Studio 2008 and the display format of the operating system is not English, an error may be thrown: “Your system does not have Visual Studio 2005 or Visual Studio 2008 installed."

This error will occur when the OS is Windows 7, Windows Vista, or Windows Server 2008, and Visual Studio 2005 or Visual Studio 2008 is installed. This error can be reproduced in the Windows 7 SDK and the Windows Server 2008 SDK.

Cause: With some non-English operating system display formats, the Windows SDK Configuration Tool is unable to parse the version number of Visual Studio as written in the registry.

Solution: There are two workarounds to the problem:

(1) Use the command-line version of Windows SDK Configuration Tool to change to the version of the Windows SDK you wish to target. For example to target the Windows 7 SDK go to the Windows SDK prompt by Clicking All Programs -> Select Microsoft Windows SDK v7.0 -> Select CMD shell. At the Windows SDK command prompt, type “ WindowsSdkVer.exe -version:v7.0 “ [without quotes]

(2) Change the OS Display Format to English (United States). Go to Control Panel and navigate to your Regional and Language Options. On the Formats tab ensure English (United States) is selected. You should now be able to use the Windows SDK Configuration Tool to target the appropriate build environment. Note: once you have changed the target you may return your OS Display Format to its original setting.

Send your thoughts to the Windows SDK Feedback alias. Tell us how you use the SDK and what we can do to improve your development experience. The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Window SDK Team

Using the Win 7 SDK Build Environment with VS 2008

wsdkblog@microsoft.com — Fri, 07 Aug 2009 20:50:00 GMT

Changes have been made to the Windows SDK build environment and how the SDK interacts with MSBUILD and Visual Studio 2008. This post applies to the RTM release of the Windows SDK for Windows 7 and .NET Framework 3.5 SP1.

What changed with the Windows SDK for Windows 7?

The Windows SDK for Server 2008 sets a registry key upon installation to identify the SDK as the “current” SDK to use when building. This key is used by the VC++ toolset in both Visual Studio 2008 and in the Windows SDK build environment:

On an X86 computer: HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows
On an X64 or IA64 computer: HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows

The Windows SDK for Windows 7 does not set this key during installation in order to avoid unexpected changes to Visual Studio 2008. To set the Windows SDK used by Visual Studio, use the Windows SDK Configuration Tool.

Out-of-the-box experience with the Windows SDK for Windows 7

If you install the Windows SDK for Windows 7 on a clean computer and create an application with the SDK build environment, the SDK will use the Windows 7 headers, libraries and tools that are included with the SDK.

If Visual Studio 2008 is installed, MSBuild and/or VCBuild will default to the headers, libraries and tools that have been previously integrated with Visual Studio 2008, in most cases, this is the (Vista-level) Windows SDK v6.0a. If this is the case, the Windows SDK build environment will display a warning when launched.

How to use the Windows SDK for Windows 7 headers, libraries and tools with Visual Studio 2008

Use the Windows SDK Configuration Tool to set the Windows 7 SDK as the “current” SDK for MSBuild and VCBuild. This will update the Windows 7 SDK build environment and the Visual Studio 2008 IDE build environment to use the Windows 7 SDK headers, libraries and tools. You can also use this tool to switch it back again.

To run the GUI version of the Windows SDK Configuration Tool, go to Start, All Programs, Microsoft Windows SDK v7.0, Visual Studio Registration, Windows SDK Configuration Tool.

Send your thoughts to the Windows SDK Feedback alias. Tell us how you use the SDK and what we can do to improve your development experience. The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Karin Meier-Magruder
Program Manager
Windows SDK Team

How to get the WinSDK Configuration Tool to work

wsdkblog@microsoft.com — Mon, 06 Oct 2008 22:10:33 GMT

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you want to build with in Visual Studio. The tool shipped with the Windows SDK for Server 2008, and bugs have since been discovered that affect different scenarios. Here’s how to get the tool working in your scenario. Instructions are different depending on which Visual Studio release and SKU you’re using. This post addresses the version of the SDK Configuration Tool that shipped in the Windows SDK for Server 2008.

Visual Studio 2008 Retail:

First, the Visual Studio 2008 SP1 patch breaks the tool. If you’ve installed the patch on VS 2008 Retail (non-Express versions), you need to first complete the workaround explained in this blog post. Read the blog post Integrating Windows SDK and VS with new SDK Configuration tool if you want background on the tool. Next, the GUI version of the tool looks like it works but it doesn’t really change the paths. This will affect you even if you haven’t installed the SP1 patch. You have to use the tool at the command line, following these steps.

To use the Visual Studio command line build environment:

1. Launch Visual Studio 2008 command prompt.

2. CD to the directory where the SDK Configuration Tool is located (by default, C:\Program Files\Microsoft SDKs\Windows\v6.1\Setup).

3. Run the SDK Configuration Tool, specifying which SDK version to make current: (Type: WindowsSdkVer.exe -version:v6.1)

4. You can now build at the command line using version v6.1 of the SDK, which is the Windows SDK for Server 2008. You can switch back to v6.0a to use the SDK components that shipped in Visual Studio 2008.

5. If you’d like to build in the Visual Studio IDE, while still in the Visual Studio command window, type: devenv /useenv

6. The SDK version you have set as “current” will remain the current SDK for the current Visual Studio session.

To use the Visual Studio IDE:

Follow the instructions above to launch the tool from the command line build environment then switch to the IDE, or use workaround # 2 in this blog post to update HKEY_CURRENT_USER to point to the version of the SDK that you wish to build with. This workaround ‘permanently’ sets the SDK version you have set as “current.” It will remain the current SDK until it is changed again through the registry. (Running Repair on Visual Studio or the Windows SDK can change this value in the registry.)

Visual Studio 2008 Express:

Read the blog post Using Visual C++ 2008 Express with the Windows SDK if you need background. The only bug on Express is that the GUI version of the tool doesn’t work. (The Visual Studio 2008 SP1 Patch does not affect Express versions.) You have to use the command line version of the tool to set the ‘current SDK’, but then you can use VS 2008 Express in the IDE or command line mode.

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.1

This command will set the Windows SDK for Windows Server 2008 (v 6.1) as the “current” SDK for Visual Studio to use. Use ‘-version:v6.1’ for the Windows Server 2008 SDK content. Use ‘-version:v6.0A’ for the Visual Studio 2008 content.

Visual Studio 2005 Retail:

On VS 2005, the tool works by overwriting your VCProjectEngine.dll.config file and a bug causes it to do so without warning, so back this file up first if you have custom settings you want to keep. Read the blog post Integrating Windows SDK and VS with new SDK Configuration tool for background on the tool. The tool works well in either GUI or command line version with VS 2005, with the exception of one scenario. The configuration tool requires that VS 2005 C++ has been run at least once. Intermittently, users will get an error that “VS 2005 must be run at least once…” even though VS2005 has already been run. This seems to affect some users that have installed VS 2005 as Administrator but are running as Limited User. You can probably get it working by running VS as an Admin.

Visual Studio 2005 Express:

The tool is not supported on Visual Studio 2005 Express. Upgrade to Visual Studio 2008 Express or set your header, library and tool paths manually.

Karin Meier
Program Manager, Windows SDK Team

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Bug Notification: VS2008 SP1 Breaks WinSDK Configuration Tool

wsdkblog@microsoft.com — Sat, 23 Aug 2008 03:27:43 GMT

Issue:
Installing Visual Studio 2008 SP1 breaks the Windows SDK Configuration tool in the Windows SDK for Windows Server 2008 and .NET Framework 3.5. This tool is used to set the version of Windows SDK headers, libraries and tools you wish to build with in Visual Studio. After installing VS 2008 SP1, the Configuration tool will crash with an unhandled exception on an X86 computer. The tool’s UI will be displayed with a blank dialog box on an X64 computer. This issue does not affect VS 2008 Express SKUs.

Cause:
The Configuration tool depends on a registry key value that is overwritten with invalid content by the Service Pack patch. After the SP1 patch is installed, the HKLM\Software\Microsoft\Microsoft SDKs\Windows\v6.0a subkey ProductVersion is set to “v6.0A”. The tool expects this value to be a build number with the format 6.xxx.xxx.xxx. On an X64 computer, an additional registry key is overwritten with the invalid value: HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v6.0A@ProductVersion.

Workaround:
Repair Visual Studio 2008 to reset the ProductVersion value.

1. Open the Control Panel and select Products and Features (Add/Remove Programs on pre-Vista operating systems)
2. Select Microsoft Visual Studio 2008 and click on Uninstall/Change. The Visual Studio 2008 setup wizard will launch.
3. When prompted, choose to Repair/Reinstall Visual Studio 2008. (This will not remove the Service Pack.)

Alternatively, advanced users can update the registry key(s) manually to set a ProductVersion value of “6.0.6001.17011”. Review the article, Windows registry information for advanced users before editing the registry.

On an X86 computer:
· HKLM\Software\Microsoft\Microsoft SDKs\Windows\v6.0a@ProductVersion = 6.0.6001.17011

On an X64 computer:
· HKLM\Software\Microsoft\Microsoft SDKs\Windows\v6.0a@ProductVersion = 6.0.6001.17011
· HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v6.0A@ProductVersion = 6.0.6001.17011

Note: An additional workaround is necessary to use the SDK Configuration in GUI mode on VS 2008. Refer to the Windows SDK Blog post, WinSDK bug notification: SDK Config Tool appears to work but fails.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

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

wsdkblog@microsoft.com — Tue, 01 Jul 2008 01:20:00 GMT

This article applies to the Windows SDK for Windows Server 2008 and .NET Framework 3.5, when used with Visual Studio 2008 (all versions). This post describes a problem with the GUI version of the Windows SDK Configuration Tool, which is used to set the version of Windows SDK headers, libraries and tools you wish to build with in Visual Studio. This article applies only to Visual Studio 2008, and does not apply to those using the Windows SDK with Visual Studio 2005. This article does not apply to the command line version of the Windows SDK Configuration Tool.

Issue: The Windows SDK Configuration Tool (GUI mode) appears to update Visual Studio 2008 header, library and executable directories, but directories are not updated. Users may not be aware of this because the SDK Configuration Tool returns a message saying that directories have been successfully updated. The user may then build applications using an unexpected set of headers, libraries and tools.

Scenario: A user has Visual Studio 2008 (any SKU) installed on her computer, and also has the Windows SDK for Windows Server 2008 and .NET Framework 3.5 installed. The user knows she can use the Windows SDK Configuration Tool to tell Visual Studio 2008 which version of the Windows SDK to use: the Windows SDK components that ship in Visual Studio 2008, or the Windows SDK components installed with the standalone Windows SDK for Server 2008.

The user runs the Windows SDK Configuration Tool and changes the “current” SDK. The tool returns a message saying the “Windows SDK Configuration Tool successfully set version X as the current version for Visual Studio 2008.” In fact, the “current version” of the SDK has not been reset.

The cause: After installing the Windows SDK for Windows Server 2008 and Visual Studio 2008 (any SKU), you’ll have two sets of SDK resources installed by default to C:\Program Files\Microsoft SDKs\Windows\:

· \v6.0A contains the SDK resources installed by Visual Studio 2008

· \v6.1 contains the SDK resources installed by the Windows SDK for Windows Server 2008

When a Windows SDK (including the Windows SDK embedded in Visual Studio 2008) is installed, it writes the “currentInstallFolder" value in both of the following keys:

· HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\

· HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SDKs\Windows\

Visual Studio 2008 looks to these keys to determine the “current” SDK. Visual Studio 2008 IDE first checks the HKCU key, and if that key is missing, it will look next in HKLM. However, the Windows SDK Configuration Tool only updates the HKLM key:

· HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SDKs\Windows\

Two workarounds are available. Start the Windows SDK Configuration Tool in command line mode, or Update HKEY_CURRENT_USER in the registry to point to the version of the SDK that you wish to build with.

Workaround option 1 (recommended): Start the Windows SDK Configuration Tool in command line mode:

1. Launch Visual Studio 2008 command prompt

2. CD to the directory where the SDK Configuration Tool is located (by default, C:\Program Files\Microsoft SDKs\Windows\v6.1\Setup).

3. Run the SDK Configuration Tool, specifying which SDK version to make current: (Type: WindowsSdkVer.exe -version:v6.1)

4. You can now build at the command line using version v6.1 of the SDK

5. If you’d like to build in the Visual Studio IDE, while still in the Visual Studio command window, type: devenv /useenv

6. The SDK version you have set as “current” will remain the current SDK for the current Visual Studio session.

Workaround option 2: Update HKEY_CURRENT_USER to point to the version of the SDK that you wish to build with:

(Modifying the registry is only recommended for advanced users, but if you have sufficient experience, you can update the HKEY_CURRENT_USER to point to a different version of the SDK. Anyone considering this should review the article, Windows registry information for advanced users before using regedit.

This workaround is to update the "CurrentInstallFolder" value in HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\ and set it to the SDK you wish for Visual Studio 2008 to use. (Installation directories shown here are default installation paths. If you chose to install the SDK to a non-default location your path will be different.)

· HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\@CurrentInstallFolder = C:\Program Files\Microsoft SDKs\Windows\v6.0A\ to build with the Windows SDK content included in VS2008;

· HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\@CurrentInstallFolder = C:\Program Files\Microsoft SDKs\Windows\v6.1\ to build with the Windows SDK content included in the Windows SDK for Server 2008.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Integrating Windows SDK and VS with new SDK Configuration tool

wsdkblog@microsoft.com — Sat, 01 Mar 2008 07:29:00 GMT

This article describes the use of the Windows SDK Configuration tool, which is included in the Windows SDK for Windows Server 2008 and .NET Framework 3.5 and works with Visual Studio 2005 and Visual Studio 2008, including Visual Studio 2008 Express SKUs.

A serious bug has been discovered with the Windows SDK Configuration Tool. This bug is not apparent as the tool appears to work correctly. Please read the blog post WinSDK bug notification: SDK Config Tool appears to work but fails, to learn more about the issue and find workaround steps.

What is the Windows SDK Configuration tool for?

The Windows SDK for Windows Server 2008 and .NET Framework 3.5, released in February, 2008, includes a new tool to help you develop more easily with Visual Studio. You can use this tool to set which version of Windows SDK headers, libraries and tools you want to build with in Visual Studio.

The Visual Studio 2008 editions are seamlessly integrated with the Windows SDK. VS2008 editions include the same Vista RTM headers and libraries that shipped in the Microsoft Windows Software Development Kit Update for Windows Vista released in March, 2007. (The SDK tools in VS2008 are more recent.) You can use these integrated Windows Vista headers and libraries right out of the box with Visual Studio 2008. If you want to use the content in another Windows SDK, the SDK Configuration Tool will allow you to do just that, by setting which SDK is the ‘current’ SDK to build with.

Updating the Windows SDK Content in Visual C++2008

You can build Win32 applications right out of the box with the Vista RTM SDK components that are embedded in Visual Studio 2008. It’s also easy to switch to the more recent components that ship with the Windows SDK for Windows Server 2008 and .NET Framework 3.5 by installing this SDK on your computer. If you install the SDK after you installed VS, you are ready to develop with the headers, libraries and tools in the SDK for Windows Server 2008. If you installed the Windows Server 2008 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set the directories.

Windows SDK headers, libraries and tools

After installing the Windows SDK for Windows Server 2008 and Visual Studio 2008 (any SKU), you’ll have two sets of SDK resources installed by default to C:\Program Files\Microsoft SDKs\Windows\:

· \v6.0A contains the SDK resources installed by Visual Studio 2008

· \v6.1 contains the SDK resources installed by the Windows SDK for Windows Server 2008

Visual Studio 2008 will point to v6.0A headers, libraries and tools, which installed with VS by default. Use the SDK Configuration Tool to update the Visual C++ directories to point to the v6.1 headers, libraries and tools that shipped with the Windows SDK for Server 2008.

How does the SDK Configuration Tool work?

The tool works by altering the Visual Studio 2008 directories through a registry key setting. (The tool works differently with Visual Studio 2005. This will be covered in a future post.)

· On an X86 computer: HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows

· On an X64 or IA64 computer: HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows

The settings “CurrentVersion” and "CurrentInstallFolder" refer to the version and location of the registered Windows SDK headers, libraries and tools. These settings get updated during Windows SDK installation or when the Windows SDK Configuration Tool is used to choose which Windows SDK content users want to use with Visual Studio 2008.

SubKey	Window SDK Version
V6.0	Windows SDK for Windows Vista and Windows SDK for Windows Vista Update
V6.0A	Windows SDK Visual Studio Components
V6.1	Windows SDK for Windows Server 2008

Visual Studio 2008 looks at this key to determine how to set the following directories:

· Visual Studio Library Directory sets the paths to use when searching for library files while building a VC++ project. It corresponds to environment variable LIB.

· The Visual Studio Include Directory sets the paths to use when searching for include files while building a VC++ project. It corresponds to environment variable INCLUDE.

· The Visual Studio Executables Directory sets the path to use when searching for executable files while building a VC++ project. It corresponds to environment variable PATH.

The VC++ 2008 Library, Include and Tool path are set upon install to the Windows SDK content that ships embedded with Visual Studio 2008. If you want to change these paths you can do so manually through Visual Studio, or use the SDK Configuration Tool to set these directories.

The SDK Configuration Tool has a GUI interface that works with the Visual Studio Retail (non-Express) SKUs, and a command line interface that works with either the VS Retail or Express SKUs. (See Using Visual C++ 2008 Express with the Windows SDK for more information on working with Visual Studio Express.)

How to use the SDK Configuration Tool in GUI mode

To launch the SDK Configuration Tool GUI interface, go to Start, All Programs, Microsoft Windows SDK v6.1, Visual Studio Registration, Windows SDK Configuration Tool.

Use the drop box to pick which version of SDK content you want to integrate with Visual Studio, and click Make Current.

How to use the SDK Configuration Tool at the command line

The SDK Configuration Tool can be used with either the GUI or command line interfaces with Visual Studio 2005 Retail or Visual Studio 2008. The tool can only be used at the command line for Visual Studio 2008 Express SKUs. (See Using Visual C++ 2008 Express with the Windows SDK.)

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.1

This will set the Windows SDK for Windows Server 2008 (v 6.1) as the “current” SDK for Visual Studio to use for headers, libraries and tools.

How to validate that Visual Studio Directories were successfully updated

Open the Visual Studio command window and check the PATH to see if the v6.1 directory has been added:

1. Start, All Programs, Visual C++ Express Edition 9.0, Visual Studio Tools, Visual Studio 2008 Command Prompt

2. At the prompt, type: PATH

How to Switch back to the SDK content that shipped ‘in the box’ with Visual Studio 2008

To restore the default directories, use the SDK Configuration Tool at the command line to make the v6.0A directories ‘current.’

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.0A

Troubleshooting:

After Visual Studio Repair, environment variables are reset. If Visual Studio is Repaired (through Add/Remove Programs), the environment variables will point back to the default VS content. You will need to use the SDK Configuration tool if you want to point to the content in the Windows Server 2008 SDK.

After Windows SDK Repair, environment variables are reset. If the Windows SDK is ‘Repaired’ (through Add/Remove Programs), the environment variables will point to Windows SDK content. You will need to use the SDK Configuration tool if you want to point to the content that shipped with Visual Studio 2008.

Please send feedback on this tool.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Using Visual C++ 2008 Express with the Windows SDK (short version)

wsdkblog@microsoft.com — Fri, 22 Feb 2008 08:50:00 GMT

This article describes what you need to do to build Win32 applications using Visual C++ Express and the Windows SDK for Windows Server 2008 and .NET Framework 3.5. A more detailed explanation including screenshots can be found here. With the Visual Studio 2008 Express versions you can build Win32 applications right out of the box. You no longer have to manually integrate the Windows SDK content with VC++ Express.

The Visual Studio 2008 editions are seamlessly integrated with the Windows SDK. VS2008 editions include the same Vista RTM headers and libraries that shipped in the Microsoft Windows Software Development Kit Update for Windows Vista released in March, 2007. The SDK tools included with VS2008 editions are more recent than those that ship in the Vista Update SDK and the Windows Server 2003 Platform SDK.

If you install another SDK, such as the Windows SDK for Windows Server 2008 and .NET Framework 3.5 after you install VS, you are ready to develop with the headers, libraries and tools in the SDK for Windows Server 2008. Read on if you installed the SDK before installing Visual Studio. (It’s easy to switch back if you want.)

Here’s how:

Step 1: Install Microsoft Visual C++ 2008 Express.

Step 2: Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

You’re done. After installing the Server 2008 SDK, the registry key is set to point to the new Server 2008 SDK (v6.1) content. If you installed the Windows Server 2008 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set the directories. If you want to switch back to the default (Vista v6.0A) headers and libraries that were installed with VS 2008, you should use the new SDK Configuration Tool to select the v6.0A SDK content.

Step 3: Use the SDK Configuration Tool to update the Visual C++ directories

The Windows SDK for Windows Server 2008 includes a new SDK Configuration Tool that sets the Visual Studio include, library and tools directories for you. This tool allows you to switch quickly between the headers, libraries and tools in the installed Windows SDK(s) and those that are embedded in Visual Studio. If you install the Windows Server 2008 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set the directories manually.

The SDK Configuration Tool has a GUI interface but it works only on the Visual Studio Retail (non-Express) SKUs. (This is scheduled be fixed in the next release.) You will use the SDK Configuration tool at the command line with VC++ Express.

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.1

This command will set the Windows SDK for Windows Server 2008 (v 6.1) as the “current” SDK for Visual Studio to use for headers, libraries and tools. Use ‘-version:v6.1’ for the Windows Server 2008 SDK content. Use ‘-version:v6.0A’ for the Visual Studio 2008 content.

Step 4: Validate that the directories were updated.

Open the VC++ Express command window and check the PATH to see if the v6.1 directory has been added.

How to switch directories back to the SDK content that shipped ‘in the box’ with VC++ 2008 Express

Use the SDK Configuration Tool at the command line to make v6.0A the current version.

You can also read the blog post Integrating Windows SDK and VS with new SDK Configuration tool for more information on the Windows SDK Configuration tool. This article describes the use of the Windows SDK Configuration tool, including how it works.

Using Visual C++ 2008 Express with the Windows SDK (detailed version)

wsdkblog@microsoft.com — Fri, 22 Feb 2008 08:24:00 GMT

This article describes what you need to do to build Win32 applications using Visual C++ Express and the Windows SDK for Windows Server 2008 and .NET Framework 3.5. A shortened, quick-start version of this article (without screenshots) can be found here. You can also read the blog post Integrating Windows SDK and VS with new SDK Configuration tool for more information on the Windows SDK Configuration tool. This article describes the use of the Windows SDK Configuration tool, including how it works.

You probably know that you can use Visual C++ Express to build .NET Framework applications immediately after installation. With the Visual Studio 2008 Express versions you can also build Win32 applications right out of the box. You no longer have to manually integrate the Windows SDK content with VC++ Express.

The Visual Studio 2008 editions are seamlessly integrated with the Windows SDK. VS2008 editions have the same Vista RTM headers and libraries that shipped in the Microsoft Windows Software Development Kit Update for Windows Vista released in March, 2007. The SDK tools that ship with VS2008 editions are more recent than those that ship in the Vista Update SDK.

Updating the Windows SDK Content in Visual C++2008 Express

You can build Win32 applications right out of the box with the Vista RTM headers and libraries. If you installed the Windows SDK for Windows Server 2008 and .NET Framework 3.5 after you installed VS, you are ready to develop with the headers, libraries and tools in the SDK for Windows Server 2008. If you installed the Windows Server 2008 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set the directories.

Step 1: Install Microsoft Visual C++ 2008 Express.

Step 2: Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

In most cases you should install the latest Windows SDK. The Windows SDK MSDN Developer Center is the place to find out the latest releases, read the release notes and link other SDK resources. The Windows SDK team blog is another good place to check for breaking news, workarounds and interesting discussion.

At the time this article was written, the latest SDK was the Windows SDK for Windows Server 2008 and .NET Framework 3.5. This SDK release supports Windows Server 2008, .NET Framework 3.5, and Windows Vista SP1 and is compatible with Visual Studio 2008 and Visual Studio 2005 SP1; including Visual Studio Express Editions. You can install this SDK on Windows Vista, Windows Server 2008, Windows Server 2003 or Windows XP SP2.

After installing the Windows SDK, you’ll have two sets of SDK resources installed to your hard drive by default to C:\Program Files\Microsoft SDKs\Windows\:

· \v6.0A contains the SDK resources installed by Visual Studio 2008 Express

· \v6.1 contains the SDK resources installed by the Windows SDK for Windows Server 2008

If you installed the Windows SDK for Windows Server 2008 and .NET Framework 3.5 after you installed VS, you are ready to develop with the headers, libraries and tools in the SDK for Windows Server 2008. After installing the Server 2008 SDK, the registry key is set to point to the new Server 2008 SDK (v6.1) content.

If you installed the Windows Server 2008 SDK before you installed Visual Studio, you will need to use the SDK Configuration Tool to set the directories. The registry key will be set to point to the default (Vista v6.0A) headers and libraries that were installed with VS 2008. If you want to switch to the new Server 2008 SDK (v6.1) content, you should use the new SDK Configuration Tool to select the v6.0A SDK content.

Step 3: Use the SDK Configuration Tool to update the Visual C++ directories to point to the Windows SDK headers, libraries and tools.

· The Visual Studio Library Directory sets the paths to use when searching for library files while building a VC++ project. It corresponds to environment variable LIB.

· The Visual Studio Include Directory sets the paths to use when searching for include files while building a VC++ project. It corresponds to environment variable INCLUDE.

· The Visual Studio Executables Directory sets the path to use when searching for executable files while building a VC++ project. It corresponds to environment variable PATH.

The VC++ 2008 Library, Include and Tool path are set on install to the Windows SDK v6.0A content that ships embedded with Visual Studio 2008.

The Windows SDK for Windows Server 2008 includes a new SDK Configuration Tool that sets the Visual Studio directories for you. This tool lets you switch quickly between the headers, libraries and tools in the SDK for Windows Server 2008 and those that are embedded in Visual Studio.

The SDK Configuration Tool has a GUI interface but it works only on the Visual Studio Retail (non-Express) SKUs. (This is scheduled to be fixed in the next release.) You can use the SDK Configuration tool at the command line with VC++ Express.

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.1

Step 4: How to validate that the Directories were updated.
Open the VC++ Express command window and check the PATH to see if the v6.1 directory has been added:

1. Start, All Programs, Visual C++ Express Edition 9.0, Visual Studio Tools, Visual Studio 2008 Command Prompt

2. At the prompt, type: PATH

How to Switch back to the SDK content that shipped ‘in the box’ with VC++ 2008 Express

To restore the default directories, use the SDK Configuration Tool at the command line to make the v6.0A directories ‘current.’

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.0A

Troubleshooting:

After Windows SDK Repair, environment variables are reset. If the Windows SDK is Repaired (through Add/Remove Programs), the environment variables will point to Windows SDK content. You will need to use the SDK Configuration tool if you want to point to the content that shipped with Visual Studio 2008.

Microsoft Windows SDK Blog : SDK Config Tool

Development with Windows SDK & DirectX SDK when Visual Studio 2008 is installed

How to set the C++ Directories manually

Windows SDK Configuration Tool May Report an Error When OS Display Format is not English

Using the Win 7 SDK Build Environment with VS 2008

How to get the WinSDK Configuration Tool to work

Bug Notification: VS2008 SP1 Breaks WinSDK Configuration Tool

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

Integrating Windows SDK and VS with new SDK Configuration tool

Using Visual C++ 2008 Express with the Windows SDK (short version)

Step 1: Install Microsoft Visual C++ 2008 Express.

Step 2: Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

Step 3: Use the SDK Configuration Tool to update the Visual C++ directories

Open the VC++ Express command window and check the PATH to see if the v6.1 directory has been added.

Using Visual C++ 2008 Express with the Windows SDK (detailed version)

Step 2: Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

Step 3: Use the SDK Configuration Tool to update the Visual C++ directories to point to the Windows SDK headers, libraries and tools.

Step 4: How to validate that the Directories were updated.Open the VC++ Express command window and check the PATH to see if the v6.1 directory has been added:

Step 4: How to validate that the Directories were updated.

1. Start, All Programs, Visual C++ Express Edition 9.0, Visual Studio Tools, Visual Studio 2008 Command Prompt

2. At the prompt, type: PATH

Step 4: How to validate that the Directories were updated.
Open the VC++ Express command window and check the PATH to see if the v6.1 directory has been added: