WinSDK Files That Shipped with Visual Studio 2008: Tools

Did you ever wonder what Windows SDK tools, headers, libraries, and reference assemblies are included in the different Visual Studio 2008 SKUs?  These Windows SDK components are embedded in all Visual Studio 2008 SKUs.  If you are looking for a particular file, you may not need to install a separate Windows SDK to get the content you need.

This table shows which tools shipped in each Visual Studio 2008 SKU.  This could save you valuable time when deciding which Visual Studio 2008 SKU is right for the project you are working on.  If you are looking for one specific tool to build your application, check here to find which VS SKUs it shipped in.

A future post will list the Windows headers and libraries that shipped in the Visual Studio 2008 SKUs, and another post will list the reference assemblies and Intellisense that shipped in Visual Studio 2008 SKUs. 

Click here to open a list of the .NET Framework and Windows Tools in Visual Studio 2008

·          “VS STD” includes all Visual Studio Retail (non-Express) products (Pro, VSTS, etc.).

·         All files install by default to [ProgramFiles]\Microsoft SDKs\Windows\v6.0A on an X86 computer, or to [ProgramFiles]Microsoft SDKs\Windows\v6.0A\X64 on an X64 computer

Comments (5)

  1. Clicking there gets me:

    XML Parsing Error: no element found


    Line Number 1, Column 1:

  2. Brian Cost says:

    jensfiederer, I am able to open the page that shows the table of tools without any issue.  Do you have your browser settings set correctly?  This is a large table and the page takes awhile to load.  Can you try on a different machine?  

    Karin Meier

    Windows SDK Team

    email: karinm(@) (remove parentheses)

  3. alenab says:

    I try to use betest.exe from vsstools and it give me an error:

    betest.exe is not a valid 32-bit application.

    Any thought?

  4. lrugen says:

    alenab – Can you tell me which operating system you are using and also confirm the version of the betest.exe tool that you are using plese.

    Lisa Rugen

    Windows SDK Team


Skip to main content