Microsoft Windows SDK Blog : Build Environment

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

Installing Win SDK for Svr 2008 after VS 2008 breaks VS command line build environment

wsdkblog@microsoft.com — Sat, 19 Apr 2008 00:36:00 GMT

Issue: After installing the Windows SDK for Server 2008, you are no longer able to build at the VS2008 command line. You receive an error that csc, vbc, and/or msbuild commands are not recognized. You are able to build without problems in the VS IDE.

Cause: The VC++ compilers that install with the Windows SDK overwrite vcvars32.bat improperly.

Workaround: Repair the VS2008 command line build environment by editing c:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat manually.

Close all instances of Visual Studio:

1. Use Notepad to edit the file %\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat. Change the top few lines where the variables are set.

Change these lines:

@SET VSINSTALLDIR=C:\Program Files\Microsoft Visual Studio 9.0
@SET VCINSTALLDIR=C:\Program Files\Microsoft Visual Studio 9.0\VC
@SET FrameworkDir=Framework32
@SET FrameworkVersion=v2.0.50727

@if "%VSINSTALLDIR%"=="" goto error_no_VSINSTALLDIR
@if "%VCINSTALLDIR%"=="" goto error_no_VCINSTALLDIR

to the following, in order to set the correct path to the frameworkdir:

@SET VSINSTALLDIR=c:\Program Files\Microsoft Visual Studio 9.0
@SET VCINSTALLDIR=c:\Program Files\Microsoft Visual Studio 9.0\VC
@SET FrameworkDir=c:\Windows\Microsoft.NET\Framework
@SET FrameworkVersion=v2.0.50727
@SET Framework35Version=v3.5

@if "%VSINSTALLDIR%"=="" goto error_no_VSINSTALLDIR
@if "%VCINSTALLDIR%"=="" goto error_no_VCINSTALLDIR

Open the VS command line build environment and verify that you can build successfully.

Please email us directly if you need additional help.

Karin Meier

Windows SDK Program Manager

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

Workaround: SDK build env fails on X86 XP with VS2005

wsdkblog@microsoft.com — Sat, 08 Mar 2008 02:30:00 GMT

This article applies to the Windows SDK for Windows Server 2008 and .NET Framework 3.5. Problem: If your usage scenario matches the one listed below, you will be unable to build in the Windows SDK command line build environment. If you type cl.exe in the SDK command window and press Enter, you will see this error:

This application has failed to start because mspdb80.dll was not found. Re-installing the application may fix this problem.

Computer setup required to repro issue:

1. Windows XP on x86 machine (which has version 5.1.2600.2180 of REG.exe)

2. Visual Studio 2005 installed, but Visual Studio 2008 is NOT installed

Cause: When the SDK build environment window is launched, the SDK file SetEnv.cmd launches Reg.exe. Reg.exe generates standard output when a valid KeyPath is specified and also generates error output when invalid Value is specified. In this scenario, the KeyPath is valid but the value doesn’t exist:

Command:

REG QUERY "%VSRegKeyPath%" /v 9.0

Output:

! REG.EXE VERSION 3.0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\SxS\VC7

Error: The system was unable to find the specified registry key or value

The second call to REG in setenv.cmd is grabbing the output from the call above and setting VSRoot=VERSION 3.0, which breaks the Windows SDK build environment. (Other versions of REG.EXE will immediately throw an error when an invalid KeyPath/Value combination is specified.)

Workaround: follow these instructions to manually edit SetEnv.cmd to remove the second call to REG:

Open up SetEnv.cmd in Notepad or another editor.
For this line:

FOR /F "tokens=2* delims= " %%A IN ('REG QUERY "%VSRegKeyPath%" /v 9.0') DO SET VSRoot=%%B

Either comment out using the REM command (like this):

REM FOR /F "tokens=2* delims= " %%A IN ('REG QUERY "%VSRegKeyPath%" /v 9.0') DO SET VSRoot=%%B

OR delete the line completely.

Save SetEnv.cmd.
Restart the Windows SDK command prompt.

||Karin Meier||Windows SDK PM||Build Environment.Samples.Community||

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.

SDK Workaround: Visual C++ cross-compilers fail on 64-bit platforms

wsdkblog@microsoft.com — Sun, 09 Sep 2007 21:08:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

On 64-bit platforms, the Visual C++ cross-compilers may fail to launch (e.g., when targeting X86 on a 64-bit platform), generating a Windows Side-by-Side error:

Failed to load system project defaults file 'C:\Program Files\Microsoft SDKs\Windows\V6.1\VC\Bin\VCProjectDefaults\ATLStatic.vsprops'. The project cannot load without this file installed. Please re-install the product.

To work around this issue, download and use Visual Studio 2008 Beta 2 or Visual C++ Express if you want to target a platform that is different than the one you are building on.

For more information on the updated Windows SDK compilers, see our post Updated Windows SDK Visual C++ Cross Compilers. The Visual C++ Team has posted an interesting article, What compiler does the compiler team use, and decoding version numbers.

SDK Workaround: MSBuild Reports a Dependency on .NET Framework SDK 2.0

wsdkblog@microsoft.com — Sun, 09 Sep 2007 01:13:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

· The Windows SDK Update for Windows Vista (RTM), March, 2007

The Windows SDK does not set the HKLM\Software\Microsoft\.NETFramework\sdkInstallRootv2.0 registry key to a string value containing the root directory of the Windows SDK installation. Some MSBuild tasks may expect this registry key to be set. If you already have the .NET Framework SDK 2.0 or Visual Studio 2005, this key will be set and you should not encounter a problem. However, if you install the Windows SDK without either the .NET Framework SDK or Visual Studio 2005, you may receive an error message from MSBuild tasks with a dependency on this key. To work around this issue set the string value of this key to the root directory of the Windows SDK installation. By default, this is: C:\Program Files\Microsoft SDKs\Windows\v6.1

Additionally, in order to use AL.exe, the ALToolPath parameter must be set and passed to msbuild. For the default install location, this can be done using the following command:

msbuild /p:ALToolPath="C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin

Updated Windows SDK Visual C++ Cross Compilers

wsdkblog@microsoft.com — Sat, 08 Sep 2007 04:49:00 GMT

During Windows SDK setup you are given the option to select VC++ compilers for every platform you wish to develop for. The Windows SDK for Server 2008 and .NET Framework 3.5 (available as a beta now) ships 5 new VC++ version 9 (Visual Studio 2008) compilers which are installed in this way:

Your host machine is…	You want to target…	You should select this SDK compiler…	And the SDK will install this compiler…
X86	X86	X86	X86 native compiler
X86	X64	X64	X86_amd64 cross-compiler
X86	IA64	IA64	X86_IA64 cross-compiler
X64	X64	X64	X64 native compiler
X64	X86	X86	X86_amd64 cross-compiler
X64	IA64	IA64	X86_IA64 cross-compiler
IA64	IA64	IA64	IA64 native compiler
IA64	X86	X86	X86_IA64 cross-compiler
IA64	X64	X64	X86_amd64 cross-compiler

The following list, created from the MSDN article How to: Enable a 64-Bit Visual C++ Toolset at the Command Line, describes the various versions of cl.exe (the Visual C++ compiler):

· x86 on x86 (X86 native compiler): Allows you to create output files for x86 machines. This version of cl.exe runs as a 32-bit process, native on an x86 machine and under WOW64 on a 64-bit Widows operating system.

· x64 on x64 (X64 native compiler): Allows you to create output files for x64. This version of cl.exe runs as a native process on an x64 machine.

· Itanium on Itanium (IA64 native compiler): Allows you to create output files for Itanium. This version of cl.exe runs as a native process on an Itanium machine.

· x64 on x86 (X86_amd64 cross-compiler): Allows you to create output files for x64. This version of cl.exe runs as a 32-bit process, native on an x86 machine and under WOW64 on a 64-bit Windows operating system.

· Itanium on x86 (X86_IA64 cross-compiler): Allows you to create output files for Itanium. This version of cl.exe runs as a 32-bit process, native on an x86 machine and under WOW64 on a 64-bit Windows operating system.

Having compiler issues? Look for the Windows SDK Workaround articles coming out this month in advance of the RC0 release of the Windows SDK for Server 2008 and .NET Framework 3.5. For example, see SDK Workaround: Visual C++ cross-compilers fail to launch on 64-bit platforms. The Visual C++ Team has posted an interesting article, What compiler does the compiler team use and decoding version numbers.

SDK Workaround: Running Visual Studio 2005 Integration fails on Vista

wsdkblog@microsoft.com — Fri, 07 Sep 2007 20:51:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

In Windows Vista, running the Visual Studio 2005 Registration Tool fails with the error "Unable to access the required files". This is because the integration tool needs to be run with elevated privileges:

Start --> All Programs --> Microsoft Windows SDK V6.1 --> Visual Studio Registration--> Integrate Windows SDK Directories with Visual Studio 2005 (on Vista, right-click and select Run as Administrator).

Alternatively, open an SDK build environment as Administrator, and run the Visual Studio 2005 Integration Tool from there.

Windows SDK Team

SDK Workaround: VCBuild fails to compile or upgrade projects

wsdkblog@microsoft.com — Thu, 06 Sep 2007 07:42:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0)

In order for VCBuild to run properly, vcprojectengine.dll needs to be registered. If vcprojectengine.dll is not registered, VCBuild.exe will fail with errors such as:

On compile: warning MSB3422: Failed to retrieve VC project information through the VC project engine object model. System error code: 127

On upgrade: Failed to upgrade project file ‘foo.vcproj'. Please make sure the file exists and is not write-protected.

To workaround this issue, vcprojectengine.dll must be manually registered. From a Windows SDK command line window (as administrator in Vista:

On an X86 machine, run:

cd %mssdk%\VC\bin

regsvr32 vcprojectengine.dll

On an X64 machine, run:

cd %mssdk%\VC\bin\X64

regsvr32 vcprojectengine.dll

SDK Workaround: .Net Framework 3.5 is not in the Windows SDK path

wsdkblog@microsoft.com — Sun, 02 Sep 2007 08:56:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

The .Net Framework 3.5 is not in the Windows SDK path. If the .Net Framework 3.5 is installed on a machine, its components (e.g. MSBuild) will not be found in the Windows SDK build environment by default. To workaround this issue, add the following to your path.

On an X86 machine:

C:\Windows\Microsoft.NET\Framework\v3.5

On an X64 or IA64 machine:

C:\Windows\Microsoft.NET\Framework64\v3.5

SDK Workaround: After Visual Studio integration, extra paths are added to the VC++ Directories

wsdkblog@microsoft.com — Sun, 02 Sep 2007 08:53:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

After running Visual Studio Registration, C:\Program Files\Microsoft SDKs\Windows\V6.1\VC\INCLUDE is added to the Include list found in Visual Studio under Tools->Options->Projects and Solutions->VC++Directories

To workaround this issue, remove C:\Program Files\Microsoft SDKs\Windows\V6.1\VC\INCLUDE from the list of include directories in Visual Studio under Tools->Options->Projects and Solutions->VC++Directories.

Windows SDK Team