Microsoft Windows SDK Blog : .NET

Windows API Code Pack for Microsoft .NET Framework

wsdkblog@microsoft.com — Sat, 13 Jun 2009 01:56:00 GMT

Excited about Windows 7 and would like to use new features from your managed application, but do not have a convenient way to do that? Always wanted to use many of the useful features from Windows Vista or older versions of Windows but could not do so because they were not available via .NET Framework?

There is help available now for some of your needs. Perhaps, you are already aware of Windows® API Code Pack for Microsoft® .NET Framework and have tried the version 0.85 or 0.80. We have just released the version 0.90 of this Code Pack. For people reading about it for the first time, Windows API Code Pack is a source code library to support targeting some new Windows 7 features and some other features existing in older versions of Windows from managed code. These features are not available via .NET Framework Class Library today. Using Windows API Code Pack you can target many of these useful Windows features without having to write interop code yourself. If this sounds familiar to VistaBridge, that is because the Windows API Code Pack evolved from it.

The Window API Code Pack includes a complete source code library, sample applications and API reference documents. You can build the included solution files to get the assemblies for use in your applications (pursuant to the attached license). And since the source code is available to you, it can be modified to extend functionality as needed.

We will discuss individual feature areas of the Windows API Code Pack in detail in subsequent posts; this post is intended to provide a brief overview of various feature areas.

Shell (including Windows 7 Libraries) – Windows Shell APIs provide a rich set of COM interfaces and functions for developers to interact with Shell. But managed developer cannot easily access these APIs unless they write their own interop layer. Shell related features in the Code Pack enable managed developers to access many of the vast resources of Windows Shell APIs in a standard .NET friendly way.

The Code Pack provides an overall hierarchy of various Shell entities like ShellItems, ShellLinks, Files, Folders, Known Folders, Windows 7 Libraries, non-file system containers, Shell icons, Thumbnails, Saved searches, Network Drives etc. Using the Code Pack APIs, you can easily traverse the Shell Namespace objects and perform the needed operations.
It also provides easy access to the Shell Property System. Developers can get or set the properties of various Shell objects they need from managed code.
An Explorer Browser control is included to allow developers to add a Windows Explorer lookalike inside their managed application.
Developers can easily use the latest features of Common File Open and Save Dialogs including custom controls in their applications. The TaskDialogs introduced in Vista is also available.
It includes rich thumbnail/icon support integrated with the Shell objects.

Since pictures are worth a thousand words, screen shots of some of the sample applications (included in the Code Pack) eloquently demonstrate the capabilities of the above features

Shell Hierarchy Tree Demo application shows how to traverse the Shell namespace starting with the Desktop object

ShellObject Browser demonstrates the integration of Common File Dialogs and various ShellObject types.

Star Backup using Libraries mimics a backup application that takes advantage of the new Windows 7 Shell Libraries.

Known Folders Browser displays all the Known Folders present in the system and show various properties for each folder. The application also uses ExplorerBrowser control to display the known folders

Windows 7 Taskbar – Taskbar features of the Windows API Code Pack provide convenient access to the new Taskbar functionality

Management of tasks and items in Jump Lists
Displaying icon overlays on the Taskbar button to convey state of the application
Displaying progress bar on the Taskbar button to show the status of time taking operations
Displaying Tabbed thumbnails for MDI and TDI applications
Ability to add Thumbnail Toolbar for most frequently used commands.

Screen shots of some of the sample applications (included in the Code Pack) demonstrating the above features

This sample application shows the management of jump lists in an application, progress bar and usage of Taskbar overlay icons

This sample application shows the Tabbed thumbnail and Thumbnail Toolbar features

The screen shot below shows an image viewer application with thumbnail toolbar exposing important commands.

DirectX Technologies – The DirectX features of Windows API Code Pack expose a wide range of Windows graphics APIs to managed developers. Many of these are new to Windows 7.

Direct3D 11.0, Direct3D 10.1/10.0 features can be used to add 3D graphics to your managed applications.
Direct 2D feature allow you to access powerful new 2D graphics APIs in your applications.
DirectWrite feature expose parts of the new text rendering APIs
Windows Imaging Component (WIC) feature makes working with images and image data convenient by exposing some WIC APIs.
Also included are some utilities for Math computations, texture loading etc.

Screen shot of a ‘Paint’ like sample application built using these features showcases some of the capabilities of the Code Pack.

Screen shot of another application showcasing the advanced texture and mesh features of Direct3D, WIC managed APIs and some utilities

Sensor Platform APIs - The Sensor feature of the Code Pack gives developers access to the new Sensor Platform APIs from managed code. Windows 7 has introduced standardized support for physical sensors, such as accelerometers and ambient light sensors. A developer can use the Code Pack to collect data reports from sensors attached to the computer and process changes received in the sensor data reports.

Screen shots of sample applications demonstrating use of accelerometer and ambient light sensor data.

Extended Linguistics Services (ELS) APIs – ELS APIs are new to Windows 7. ELS feature of the Code pack provides managed developers the ability to detect the script or language being used and adjust the user experience accordingly.

Power Management – provides managed code access to power settings and notifications for related changes.

Screen shot of the sample application that demonstrates the use of power management related APIs

Application Restart and Recovery – lets a managed application save data and state information before an application exits because of an unhandled exception.

The screen shot of a sample application below demonstrates this feature. In the event of an application crash, the library allows the application to recover its data and when restarted by the system, it can load the previously saved data

Network List Manager APIs – provides managed code access to network details
Managed code access to Command Link control and System defined Shell Icons

There are many other samples (available both in C# and VB.NET in some areas) included in the Code Pack. Please download and play with the Windows API code pack and samples to explore its full potential. We are currently working on fixing bugs and preparing for the final update around the Windows 7 RTM release. Please let us know if you find any issues or have any suggestions, by using the Discussions or Issues tab and help us make the Windows API Code Pack better.

More detailed post on different feature areas coming soon.

Sumit Kumar

Program Manager, Windows SDK Team

.NET Terrarium 2.0 source code now available!

wsdkblog@microsoft.com — Wed, 16 Jul 2008 18:09:00 GMT

The Windows SDK team is happy to announce the availability of the source code for .NET Terrarium 2.0 on http://www.codeplex.com/terrarium2 . For those who are not familiar with Terrarium, I’ll provide a little history. It is a game that was created by members of the .NET Framework team in the .NET Framework 1.0 timeframe and used initially as an internal test application. At various conferences and online chats, Terrarium provided a way for developers to learn about the new .NET programming model and language. By making the source code for .NET Terrarium 2.0 available, we hope to provide a fun and interesting opportunity for developers to try out and learn the latest advances in the .NET Framework.

Many thanks to Bil Simser, a Microsoft MVP, who brought the interest in Terrarium to our attention, volunteered to help coordinate the project, and patiently waited while we prepared to release the source code. Read Bil's blog post on how it works, what's changed, and what the future holds for this ever-evolving project.

Lisa Supinski

Group Manager, Windows SDK team

Released: Visual Studio 2008 with embedded Windows SDK Components

wsdkblog@microsoft.com — Sat, 01 Dec 2007 01:56:00 GMT

I’m pleased to announce on behalf of the entire Windows SDK team, that we have released Windows SDK components with Visual Studio 2008 and .NET Framework 3.5. Windows SDK components ship embedded into just about all of the Visual Studio 2008 versions. The Windows SDK team understands that developers have traditionally used the Windows SDK components hand-in-hand with Visual Studio, and Visual Studio 2008 will be no exception. The Windows SDK team has worked hard over the last year plus to better understand how developers use the two products together. This research has resulted in a seamless integration between this Windows SDK and Visual Studio 2008, which for this release are one in the same.

There will be no separate, standalone web release of this version of the Windows SDK. You can download the free Visual Studio Express editions, which have some Windows SDK components. If you want a full standalone Windows SDK for use with Visual Studio 2008, you can download the Microsoft® Windows® Software Development Kit Update for Windows Vista™ that was released in March, 2007. This SDK has the same set of (Vista RTM) SDK headers and libraries that are included in Visual Studio 2008. However, the SDK tools that ship with VS2008 are more recent than those that ship in the Vista Update SDK.

If you want an SDK that corresponds to the prerelease version of Windows Server 2008, download the Windows SDK for Windows Server 2008 Release Candidate 0 and .NET Framework 3.5 Beta2 this SDK contains Visual Studio 2008 Beta 2 versions of .NET Framework 3.5 content. The release version of this SDK will ship at the same time as Windows Server 2008.

· MSDN subscribers can download Visual Studio 2008 from the MSDN subscription site.

· If you do not subscribe to MSDN, you can download a free 90-day trial edition of Visual Studio 2008 Team Suite.

o This edition contains all Windows SDK components shipping with this release of Visual Studio.

· You can also download the Visual Studio 2008 Express editions, which are much smaller and totally free.

o These editions only have a subset of Windows SDK components, but all you need to complete supported development scenarios in those editions.

· If you want to install only the .NET Framework 3.5 runtime, you can download it here.

The .NET Framework 3.5 specific content can be found in the default SDK install folder of any Visual Studio 2008 edition under C:\Program Files\Microsoft SDKs\Windows\v6.0A\

o \Bin contains tools like SqlMetal.exe

o \Bootstrapper directory has bootstrapper packages for developers who want to use Visual Studio 2008 to deploy their applications

o \FXCop contains the FXCop installer

o \Include & \Lib contains the Windows Headers and Libraries that shipped with Microsoft® Windows® Software Development Kit Update for Windows Vista™

Your feedback is welcome and appreciated,

Pat Litherland

Windows SDK Program Manager

Windows SDK for Windows Server 2008 RC0

wsdkblog@microsoft.com — Wed, 26 Sep 2007 23:26:00 GMT

The latest prerelease Windows SDK is now available for installation! This SDK release supports Windows Server 2008 RC0 and .NET Framework 3.5 Beta2.

The SDK is compatible with the RTM release of Visual Studio 2005 SP1; including Visual Studio Express Editions. In addition the SDK is shipping the Visual Studio 2008 Beta2 versions of the C++ command line toolset and CRT.

As always, please look over the Release Notes for a description of known issues with the SDK. A few important items of note are the following:

1. This release of the SDK is an ISO-only download. For more tips on handling an ISO, please take a look Copying the contents of ISO files section of the Troubleshooting SDK Download/Setup Problems blog post.

2. To take advantage of new VS 2008 capabilities when building SDK samples please review the Release Notes about what steps are required.

3. The .NET Framework documentation, samples, and tools in this SDK aligns with .NET Framework 3.5 Beta2.

Here’s a quick rundown of what’s new in this SDK:

· The latest set of documentation, samples, and tools for Windows including .NET Framework 3.5 development.

· A new C++ compiler and associated CRT

· This SDK will install side-by-side with Visual Studio 2008 Beta2.

We encourage you to install this SDK on a test machine and let us know what you think.

Barry R. Butterklee

Windows SDK Release PM

barrybu@microsoft.com

SDK Workaround: Samples Fail to Compile with Debug:Itanium error

wsdkblog@microsoft.com — Mon, 10 Sep 2007 23:14: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

Some samples may fail to compile in the SDK build environment with the following error:

vcbuild.exe : error VCBLD0004: Project 'C:\buildall_hxs\local\sampleexecutables\Technologies\DirectoryServices\BEREncoding\CP\BerEncoding\BerEncoding.vcproj' does not contain a configuration called 'Debug|Itanium'

This error occurs because platform configurations are listed alphabetically by default in a project or solution file created by Visual Studio. If Debug|Itanium is a supported configuration, it will be listed first in the samples’ solution and/or project files.

To workaround this issue, use a configuration switch to specify what platform you wish to build for:

Msbuild *.sln /p:platform=Win32

Msbuild *.sln /p:platform=X64

VCbuild *.vcproj /platform:Win32

VCbuild *.vcproj /platform:X64

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

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: Visual Studio 2005 is Required for .NET Compact Framework Development

wsdkblog@microsoft.com — Sun, 02 Sep 2007 08:37: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 SDK provides documentation and sample code that targets the .NET Compact Framework. However, actual development of .NET Compact Framework applications requires Visual Studio 2005. When building a sample that depends on the .NET Compact Framework, you might see this error:

C:\Sample\Foo.csproj(57,11): error MSB4019: The imported project "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Microsoft.CompactFramework. CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

To workaround this issue, download and install the .NET Compact Framework 2.0 Redistributable or the pre-release .NET Compact Framework 3.5 Beta1 Redistributable.

Windows SDK Team

New Windows SDK Available to Download

wsdkblog@microsoft.com — Tue, 31 Jul 2007 01:11:00 GMT

It has been barely 3 months since we shipped the previous Windows SDK prerelease; and here we are today shipping another prerelease version of the Windows SDK. This SDK coincides with the release of Microsoft® Visual Studio® 2008 Beta2 and Microsoft® .NET Framework 3.5 Beta2. If you want to be on the cutting edge of .NET Framework 3.5 development, this SDK is for you. Our SDK even has a catchy new name, the Windows SDK for Windows Server® 2008 and .NET Framework 3.5.

Here’s a quick rundown of what’s new in this SDK:

· The latest set of documentation and samples for .NET Framework 3.5 development.

· New and updated tools for .NET Framework 3.5 development

· A new C++ compiler and associated CRT

· This SDK will install side-by-side with Microsoft® Visual Studio® 2008 Beta2.

As was the case with our previous prerelease SDK, this SDK is compatible with the RTM release of Microsoft® Visual Studio® 2005 SP1 and the Microsoft® Visual Studio® Express Editions, which are available to download, free of charge.

As always, we strongly recommend reading the Release Notes for a description of known issues with this SDK. A few items worth calling out are the following:

· To take advantage of .NET Framework 3.5 features, such as new samples or tools, you’ll need to install the Microsoft® .NET Framework 3.5 Beta2

· If you want to use Microsoft® Visual Studio® 2005 with existing SDK C++ samples you can. If you want to take advantage of and try out the latest C++ command line compiler that ships in this SDK on those same samples, you’ll need to upgrade those sample projects as described in the Release Notes.

· This release of the SDK is an ISO-only download. This means that you will need to download the entire ISO and then either burn it to a DVD to use in your local DVD drive, mount it virtually as if it were another drive, or copy the contents locally, in order to run the SDK’s setup.exe. More details about how to work with the DVD ISO image can be found at the download page for the SDK

We encourage you to install this SDK on a test machine and let us know what you think.

Barry Butterklee

Windows SDK Release PM

barrybu@microsoft.com

What is .NET 3.5?

wsdkblog@microsoft.com — Wed, 13 Jun 2007 00:14:00 GMT

This is a question we get quite frequently and so we thought we'd share a couple of blog posts by Microsoft Evangelist Daniel Moth.

In the following post, Daniel hghlights what is new to .NET 3.5 (with links to further information about several new or updated assemblies) as well as the concept of red-bits vs. green bits.

http://www.danielmoth.com/Blog/2007/06/net-framework-35.html

Another key related bit of information has to do with versioning as many times folks are confused as to the Minor, Build and Revision parts of the .NET Framework versions. Daniel clears a bit of that up with the following post:

http://www.danielmoth.com/Blog/2007/05/clr-v20-remains-at-same-version.html

.NET Framework 3.5 Beta 1 on MS Download Center

wsdkblog@microsoft.com — Wed, 09 May 2007 07:05:00 GMT

There's no longer a need to download the Visual Studio “Orcas” beta to get the .NET Framework 3.5 bits. The .NET Framework 3.5 Beta 1 is a preview release of the latest version of the .NET Framework and works with the Windows SDK for Windows Server code name “Longhorn” and .NET Framework 3.5.

.NET Framework 3.5 is planned to release at the end of 2007 and will ship with Visual Studio code name ”Orcas” and will also continue to be available for separate download from MSDN.

For more detail about the features being introduced in .NET Framework 3.5 and Visual Studio code name “Orcas”, click here. For more information about the .NET Framework, click here.

Karin Meier

Samples PM, Windows SDK

New Windows SDK Available!

wsdkblog@microsoft.com — Thu, 26 Apr 2007 19:16:00 GMT

Let me start off by introducing (or more precisely) re-introducing myself. My name is Barry Butterklee and as of the middle of March, I started a new role on the SDK team: Release PM for the Windows SDK for Windows Server code name “Longhorn” and .NET Framework 3.5. Yes, the name of the SDK is quite the mouthful, so for the remainder of this post, I will simply refer to it as the Windows SDK or the SDK. It has been quite the experience coming up to speed as a Release PM just a few short weeks before we ship; fortunately our team has a lot of experience shipping SDKs that I was able to leverage.

Now, back to the main news of this post; namely that the Windows SDK for Windows Server code name “Longhorn” and .NET Framework 3.5 (I promise, this is the last time I use the long SDK name in this post) is available for download (note: the download servers are under heavy load right now and you might need to refresh the download url)! This release of the Windows SDK is designed to operate with Beta3 of Windows Server code name “Longhorn”. The SDK is compatible with the RTM release of Microsoft® Visual Studio® 2005 SP1. Express Editions of Microsoft® Visual Studio® are available to download from the Microsoft® Visual Studio® Express Editions, free of charge. As always, we strongly recommend reading the Release Notes for a description of known issues with the SDK.

One very important item from the Release Notes is that this release of the SDK is an ISO-only download. This means that you will need to download the entire ISO and then either burn it to a DVD to use in your local DVD drive, mount it virtually as if it were another drive, or copy the contents locally, in order to run the SDK’s setup.exe. More details about how to work with the DVD ISO image can be found at the download page for the SDK.

Another item of interest relates to the second part of the SDK’s name; specifically .NET Framework 3.5. The SDK not only ships content aligned with Windows Server code name “Longhorn”, but also content that aligns with the upcoming .NET Framework 3.5. The .NET Framework 3.5 is available with the Beta1 pre-release editions located at Microsoft® Visual Studio®, Code Name "Orcas" Downloads and is required in order to take advantage of any tools or samples that have a dependency upon the .NET Framework 3.5.

One cool new feature in the SDK, that has been frequently requested is, an alphabetized list of the APIs in the documentation. It is located in the documentation under the Getting Started | Platform Information section and contains lists of APIs (also constants, enumerations, and structures) grouped by managed APIs, Win32 and COM APIs, new to Vista APIs, and one large over-arching list of all these APIs. Also, the SDK contains millions of samples, thousands of tools, and has been known to cause people to jump for joy after they’ve installed it. Well perhaps the part about the millions of samples and thousands of tools is a little bit of an exaggeration.

We encourage you to install this SDK on a test machine and let us know what you think.

Barry Butterklee

Windows SDK Release PM

barrybu@microsoft.com

Troubleshooting sample building issues on X64, post 6

wsdkblog@microsoft.com — Wed, 25 Apr 2007 18:52:00 GMT

Here's another tip for troubleshooting issues with Windows Vista SDK samples on X64. Some samples depend on the .NET Compact Framework, which is not included in the Windows SDK. The X86 version of the .NET Compact Framework 2.0 (SP2) has full support for 64-bit operating systems, including Windows Vista Business 64-bit edition, Windows Vista Enterprise 64-bit edition, Windows Vista Home Basic 64-bit edition, Windows Vista Home Premium 64-bit edition, and Windows Vista Ultimate 64-bit edition.

6. Error: C:\Sample\Foo.csproj(57,11): error MSB4019: The imported project "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Microsoft.CompactFramework.CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Problem: This sample requires the .NET Compact framework, which is not included with the Windows SDK.

Workaround: Download and install the .NET Compact Framework 2.0 Service Pack 2 Redistributable http://www.microsoft.com/downloads/thankyou.aspx?familyId=aea55f2f-07b5-4a8c-8a44-b4e1b196d5c0&displayLang=en

Karin Meier

Windows SDK Samples Program Manager

Troubleshooting sample building issues on X64, post 4

wsdkblog@microsoft.com — Mon, 23 Apr 2007 17:58:00 GMT

Here's another workaround for building Windows Vista SDK samples on X64. Look for my earlier workaround posts and keep checking for more. New to 64-bit programming? Matt Pietrek's MSDN Magazine article, "Everything You Need To Know To Start Programming 64-Bit Windows Systems" will help.

4. Error: Msbuild Reports a Dependency upon the Microsoft .NET Framework SDK 2.0.

Problem: 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. However, 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 installed, this key would 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.

Workaround: 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.0.

Karin Meier

Windows SDK Samples Program Manager

Troubleshooting sample building issues on X64, post 1

wsdkblog@microsoft.com — Sat, 21 Apr 2007 03:05:00 GMT

Are you having problems building some of the Windows Vista SDK samples on an X64 machine? This is the first of a series of posts with workarounds to get you building. I’ll be following up with more. Have you found workarounds to other issues? Share them here or email me.

1. Error that affects everyone building managed samples with the .NET Framework: SetEnv.cmd uses X86 framework

Problem: A bug in the SDK build environment prevents x64 from pointing to the 64bit framework directory. (Invoking SetEnv.cmd with the /x86 parameter will cause the build environment to use the x86 frameworks.) To use the x64 frameworks you will need to update a file to point to the x64 framework. (This issue has been fixed in the Windows SDK for Microsoft Windows Server code name “Longhorn” and .Net Framework 3.5.).

Workaround: You will need administrator privileges to perform this. On Vista, Right click Notepad and run as Administrator. From within Notepad, open Bin\SetEnv.Cmd and change line number 204 from:

SET FxTools=%windir%\Microsoft.NET\Framework\v2.0.50727

to

SET FxTools=%windir%\Microsoft.NET\Framework64\v2.0.50727

save your changes to SetEnv.Cmd.

Karin Meier

Windows SDK Samples Program Manager