Microsoft Windows SDK Blog : Windows SDK for Server 2008

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

Installing Windows SDK for Server 2008 (v6.1) after VS2008 SP1 causes conflicts with Security Update (KB971092)

wsdkblog@microsoft.com — Fri, 07 Aug 2009 23:57:00 GMT

Issue: If you install the Windows SDK for Windows Server 2008 and .NET Framework 3.5, on top of Visual Studio 2008 Service Pack1, some CRT files will revert back to RTM version. (See this post for more information about this issue) This can cause conflicts when you install patches or updates such as the Security Update for Microsoft Visual Studio 2008 Service Pack 1: July 28, 2009 (KB971092), which may lead to compile errors similar to this:

· error C2039: '_Swap_adl' : is not a member of 'std' c:\program files\microsoft visual studio 9.0\vc\include\xutility 2764

· error C3861: '_Swap_adl': identifier not found c:\program files\microsoft visual studio 9.0\vc\include\xutility 2764

Cause: This problem occurs when you install the Windows SDK for Windows Server 2008 and .NET Framework 3.5 on top of a post-RTM Visual Studio 2008 Service Pack, Feature Pack, or QFE. Visual Studio 2008 and the Windows SDK share compiler and CRT packages. Because the Windows SDK v6.1 includes the RTM version of the CRT, installing the Windows SDK second causes any non-versioned CRT files to be reverted back to Visual Studio 2008 RTM version. When you install a service patch, the patch will assume that all the SP1 files are still present.

Workaround: Ensure that you are using the Visual Studio 2008 SP1 version of the CRT by installing the Windows SDK for Windows Server 2008 and .NET Framework 3.5 first, then re-installing Visual Studio 2008 SP1. Then you can apply the Security Update.

Caution: Running “Repair” on the Windows SDK will cause the CRT files to go back to RTM state and should be avoided.

Karin Meier-Magruder
Program Manager
Windows SDK 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.

Win SDK for Server 2008 plus VS2008 causes double X64 platform entries in VC directories

wsdkblog@microsoft.com — Fri, 12 Jun 2009 23:57:00 GMT

Issue: Installing the Windows SDK for Windows Server 2008 after Visual Studio 2008 Standard on a computer with an X64 operating system corrupts VC directories, causing a double X64 entry

Scenario: You probably have this issue if your computer setup matches the setup described below:

1. Visual Studio 2008 Standard is installed on an X64 OS. To determine what version of Visual Studio you are using, launch Visual Studio, choose Help, About Visual Studio.

2. The Windows SDK for Server 2008 and .NET Framework 3.5 is installed (this is v6.1).

3. The VC++ Directories Platform Entries are corrupted. To determine if your directories are corrupted, launch the VS IDE and go to tool->options->projects and solutions->VC++ Directories. If the entries in the drop down “Platform” box appear as "x86", "x64" and "x64", your directories are corrupted. If the platform entries appear as "x86", "x64" and "Itanium", you do not have this issue.

4. It is not possible to create an X64 target. Neither of the X64 directory entries work.

Cause: The installation order of the compiler components that ship with the Windows SDK for Server 2008 creates the problem. Because Visual Studio Standard does not have ia64 support it does not install the file VCProjectIA64Platform.dll. The Windows SDK does support IA64 development and does install this file. However Visual Studio VC++ is a 32-bit application and requires an X86 version of the file. The Windows SDK installs a 64-bit version of the VC compiler/CRT package on 64-bit operating systems. This package includes the 64-bit version of VCProjectIA64Platform.dll, which causes the double directory entry. This issue has been fixed in later releases of the Windows SDK.

Workaround: Pick one of the following workarounds:

1. If you do not need to build targeting IA64, you can simply delete IA64.VcPlatform.config from %ProgramFiles(x86)%\Microsoft Visual Studio 9.0\VC\vcpackages.

2. If you have the Windows Server 2008 SDK installed on an X86 computer, you can copy the x86 version of VCProjectIA64Platformd.dll and drop it to %ProgramFiles(x86)%\Microsoft Visual Studio 9.0\VC\vcpackages.

3. If the above workarounds don’t work for your situation, download the Windows SDK for Server 2008 ISO package. Find the file named "\Setup\vc_stdx86.cab\FL_VCProjectIA64Platform_dll_76114_76114_x86_ln.3643236F_FC70_11D3_A536_0090278A1BB8". Rename the file “VCprojectIA64Platform.dll”. Copy it to %ProgramFiles(x86)%\Microsoft Visual Studio 9.0\VC\vcpackages.

Note: Running “Repair” on the Windows SDK will revert these fixes.

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