Home Dashboard Directory Help
Search

WinSDK 7.1, .Net 4: Windows SDK Configuration Tool fails with only VS2010 installed. by Nicolas.Drouin


Status: 

Closed
 as Fixed Help for as Fixed


7
0
Sign in
to vote
Type: Bug
ID: 564354
Opened: 5/31/2010 8:07:13 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description


Looks like the Windows SDK team forgot you when building their latest tool! ;o)

http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/ed2e77a7-1909-44cb-b297-d9bb2b1a5c0c

Windows SDK Configuration Tool Error
Your system does not have Visual Studio 2005 or Visual Studio 2008 installed.

Posted here to ensure followup of both teams.

Regards,

-Nick
Details
Sign in to post a comment.
Posted by Koichi Senada on 2/10/2011 at 12:13 AM
Please take a look at the reasons and the workaround.
http://blogs.msdn.com/b/windowssdk/archive/2009/08/21/windows-sdk-configuration-tool-may-report-an-error-when-os-display-format-is-not-english.aspx
It appears to me, that the tool developers haven't paid proper attention to the possibility of Visual Studio being installed on a machine with display language different from english.
I hope, this will be fixed.
Posted by SoftNado on 12/26/2010 at 9:24 AM
Why this issue still not fixed.
Posted by msbhvn on 7/19/2010 at 12:50 PM
Quote: The proper way to get the VC++ 2010 Express SKU to use the 7.1 library is to right click the project file and to choose to use the 7.1 Toolset.

So I have to manually alter the properties of every single project in every single solution I ever want to build from now on because you can't (or, as I suspect, won't) fix this? At least show us how to do a workaround with the default project settings (like enabling the PSDK to be used in VC2005 Express)!
Posted by Microsoft on 6/17/2010 at 11:29 AM
Hi Foxyshadis,
The proper way to get the VC++ 2010 Express SKU to use the 7.1 library is to right click the project file and to choose to use the 7.1 Toolset.
Here is a blog post about the build environment in the 7.1 SDK that may help: http://blogs.msdn.com/b/windowssdk/archive/2010/04/01/windows-sdk-build-environment-upcoming-features-and-improvements.aspx.

Thanks,
Chris Hubbard
Windows C++ SDET
Posted by foxyshadis on 6/10/2010 at 4:48 PM
Hello, I have to push back here. The Win7.1 SDK contains the x64 libraries and is the officially documented way of obtaining the x64 build environment for Visual C++ 2010 Express. Since the x64 libs are not in VS 2010 Express, a way is needed to force VS 2010 to use the 7.1 library instead of its own. Thank you.
Posted by Microsoft on 6/4/2010 at 10:16 AM
Hi,
Thank you for pointing this out. In this case, all of the headers and libraries and tools that shipped with the Win 7.0 SDK are also in VS 2010. It is desired that the SDK Configuration Tool doesn't work with VS 2010.

If you have any further questions, or comments, please let me know chrishu at microsoft dot com.

Thanks,
Chris Hubbard
Windows C++ SDET
Posted by Microsoft on 5/31/2010 at 5:02 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by Koichi Senada on 2/10/2011 at 12:17 AM
http://blogs.msdn.com/b/windowssdk/archive/2009/08/21/windows-sdk-configuration-tool-may-report-an-error-when-os-display-format-is-not-english.aspx

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.