Release Notes for Windows® Software Development Kit (SDK) for Windows 7 and .NET Framework 3.5 Service Pack 1: Beta
Welcome to the beta edition of the Microsoft Windows Software Development Kit (SDK) for Windows 7 and .NET Framework 3.5 Service Pack 1.
The Windows SDK contains a set of tools, code samples, documentation, compilers, headers, and libraries that developers can use to create applications that run on Microsoft Windows. You can use the Windows SDK to write applications using the native (Win32/COM) or managed (.NET Framework) programming model.
For access to additional resources and information, such as downloads, forum posts, and the Windows SDK team blog, go to the Windows SDK Developer Center.
This release of the Windows SDK does not include a .NET Framework Redistributable Package. Windows 7 Beta includes .NET Framework 3.5 SP1. Windows Vista and Windows Server 2008 include .NET Framework 3.0.
Users running Windows Server 2003 and Windows XP must install the .NET Framework 3.0 or 3.5 SP1 to run and develop .NET Framework applications. Some samples and tools included in the Windows SDK also require you to install .NET Framework 3.5 SP1.
Along with content that ships in the Windows SDK, Microsoft offers additional free developer tools and resources that you might find helpful, including:
· Debugging Tools for Windows can be used to debug drivers, applications, and services on systems running Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 as well as for debugging the operating system itself. Versions of the Debugging Tools for Windows package are available for 32-bit x86, native Intel Itanium, and native x64 platforms.
· LUA Buglight™ is a tool to help both developers and IT professionals (sysadmins) identify the specific causes of admin-permissions issues (LUA bugs) in desktop applications running on Windows XP, Windows Server 2003, or Windows Vista. Once the specific causes have been identified, the bugs can more easily be resolved by fixing the app's source code, or by making configuration changes, allowing the app to work correctly for non-admin users.
· Microsoft .NET Framework 3.0 is Microsoft's managed code programming model building applications on Windows clients, servers, and mobile or embedded devices. It combines the power of the .NET Framework 2.0 with four new technologies: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace (WCS, formerly InfoCard). The .NET Framework 3.0 ships with Windows Vista and Windows Server 2008.
· Microsoft .NET Framework 3.5 SP1 is the latest update of the .NET Framework, and contains many new features that are compatible with both .NET Framework 2.0 and .NET Framework 3.0. The .NET Framework 3.5 SP1 includes several fixes for .NET Framework 2.0 3.0, and 3.5.
· Microsoft Visual Studio Express is a set of free, lightweight and easy-to-use tools for the hobbyist, novice, and student developer.
· Microsoft Windows PowerShell™ command-line shell and scripting language helps IT Professionals achieve greater productivity. Using a new admin-focused scripting language, more than 130 standard command-line tools, and consistent syntax and utilities, Windows PowerShell allows IT professionals to more easily control system administration and accelerate automation. More information on Windows PowerShell is available from the PowerShell Team Blog and the Windows PowerShell Technology Center.
· Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation) provides developers with support for building workflow-enabled applications using Windows Workflow Foundation.
· Windows Server 2008 Developer Center is the official site about development and management of applications on the Windows Server 2008 platform. The Developer Center includes product information, news, tools, and code samples.
· Windows SDK Developer Center is the official site about development using the Windows SDK and provides information about the SDKs and links to the Windows SDK Blog, Forum, online release notes and other resources.
The contents included in the Windows SDK are licensed to you, the end user. Your use of the SDK is subject to the terms of an End User License Agreement (EULA) accompanying the SDK and located in the \License subdirectory. You must read and accept the terms of the EULA before you access or use the SDK. If you do not agree to the terms of the EULA, you are not authorized to use the SDK.
This release of the Windows SDK supports Microsoft Visual Studio 2005 SP1, Microsoft Visual Studio 2008 SP1, and the Microsoft Visual Studio 2008 Express Editions. Express Editions of Visual Studio are available to download from the Visual Studio Express site free of charge.
This release of the Windows SDK supports x86, x64, and IA64 platform architectures for building and running applications on Windows XP SP3, Windows Server 2003 R2, Windows Vista, Windows Server 2008, and Window 7 Beta.
To optimize your Windows SDK setup experience, we strongly recommend that you install the latest updates and patches from Microsoft Update before you begin installing the Windows SDK.
We recommend that the Windows SDK be installed on a clean computer or completely uninstall any pre-releases of the .NET Framework, the Platform SDK, the Windows SDK and their dependencies before installing this release. These older pre-release components might interfere with this release, causing setup to fail or break functionality.
You might see more than one Windows SDK product listed in the Upgrade Options screen during SDK installation. See Section 4.2 for information on uninstalling SDK components.
These release notes use <install folder> to refer to the installation folder for the Windows SDK. By default, this folder is C:\Program Files\Microsoft SDKs\Windows\v7.0.
The complete DVD ISO installation of the Windows SDK requires 1.4 GB or more disk space to install successfully. Please verify that the computer you are installing to has at least the minimum required disk space before beginning setup. If the minimum required disk space is not available, setup will return a fatal error.
This version of the Windows SDK is available as a DVD ISO image. To install it:
1. Burn the ISO to DVD media or mount it on a virtual drive. From that ISO, double-click setup.exe to begin the SDK setup
2. Follow the instructions in the Windows SDK Setup wizard
Note: If you are installing the SDK to a custom location, the Microsoft Document Explorer and the ATL/MFC runtime will not be installed by the Windows SDK. See section 5.2.2 for more information on this issue.
Access the Windows SDK shortcuts through the Start menu (Start, All Programs, Microsoft Windows SDK). The Start menu folder contains shortcuts to:
· The SDK build environment command window
· Windows SDK Release Notes
· Windows SDK documentation
· Samples Reference
· Windows SDK Configuration Tool (located under Visual Studio Registration)
If you intend to use .NET Framework components, install .NET Framework 3.5 SP1 from the Microsoft Download Center.
If you intend to use Microsoft Visual Studio 2005, install Microsoft Visual Studio 2005 SP1 and Visual Studio 2005 Extensions for .NET Framework 3.0 from the Microsoft Download Center.
Note: If you intend to use Visual Studio 2005 to develop .NET Framework applications, you must install the Windows SDK before installing the Visual Studio 2005 Extensions for .NET Framework 3.0.
If you intend to use Microsoft Visual Studio 2008, install Visual Studio 2008 SP1 from the Microsoft Download Center.
Note: Visual Studio 2008 Extensions for .NET Framework 3.0 are included with Visual Studio 2008.
Several applications need to be uninstalled separately from Add/Remove Programs (Programs and Features on Windows Vista or later) in order to remove all Windows SDK components:
· Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1: Beta
· Microsoft FxCop 1.35
· Microsoft Document Explorer
· Microsoft Visual C++ Compilers 2008
You might have installed some of these applications with another product besides the SDK. Removing those applications will make those applications unavailable for other applications that might use them. For example, the Microsoft Visual Studio offline documentation has a dependency on Microsoft Document Explorer.
In order to utilize Windows SDK headers, libraries, and tools within Microsoft Visual Studio, the SDK-provided Windows SDK Configuration Tool must be run. The Windows SDK Configuration Tool must be run for each user on Windows Vista or later. You can build Win32 applications right out of the box with the Vista SDK components that are embedded in Visual Studio 2008 (Windows headers and libraries, tools and reference assemblies). You can switch to the more recent components that ship with the Windows SDK for Windows 7 by using the Windows SDK Configuration Tool. 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 SDK. If you installed the Windows 7 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set Visual Studio directories back to the Windows 7 SDK content. To run the Windows SDK Configuration Tool, go to Start > All Programs > Microsoft Windows SDK v7.0 > Visual Studio Registration > Windows SDK Configuration Tool (on Windows Vista or later, right-click and select Run as Administrator).
When building Samples, do so in a directory outside c:\program files to which you have write access. The SDK build environment supports building samples from makefiles, Visual Studio project files or Visual Studio solution files. To build from the command line:
1. Copy the sample to a working folder not under c:\program files. Copying to a location other than c:\program files makes it possible to maintain a pristine copy of the SDK samples and avoid issues when writing to files and directories located under c:\program files.
2. Open the Windows SDK CMD shell (Start > All Programs > Microsoft Windows SDK v7.0, CMD Shell).
3. Build the sample from the command line as follows:
· Build a makefile by typing nmake
· Build a .csproj file by typing msbuild *.csproj /p:platform=[ win32 | X64 | IA64]
· Build a .vbproj file by typing msbuild *.vbproj /p:platform=[ win32 | X64 | IA64]
· Build a .sln file by typing msbuild *.sln /p:platform=[ win32 | X64 | IA64]
· Build a .vcproj by typing vcbuild *.vcproj /platform=[ win32 | X64 | IA64 ]
When building with MSBUILD, you should specify a target platform. If a project is configured to build for several different platform types and if you don't specify which platform you wish to build for, the first platform listed in the solution or project file will be built. Configurations are listed in alphabetical order by Visual Studio, so ‘Itanium’ may be the first configuration listed.
If you want to build an application configured for an X86 machine, specify ‘win32’:
msbuild mysample.vbproj /p:platform=win32
If you want to build an application configured for an X64 machine, specify ‘X64’:
msbuild mysample.vbproj /p:platform=X64
Samples demonstrating .NET Framework 3.0 and 3.5 SP1 can be found individually in the SDK documentation. Each sample has its own description page. From each sample page, you can view the source files for those samples as well as individually download all the files of that sample to a chosen location. The .NET Framework samples can be accessed in bulk by directly opening the sample .zip files located in <install folder>\Samples.
To set the build environment, use the setenv.cmd tool within a debug cmd shell by following the steps below..
1. Launch the Windows SDK build environment. From the Start menu, click on All Programs > Microsoft Windows SDK v7.0 > CMD Shell.
Set the build environment. At the prompt, type:
"C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\setenv.cmd" [/target]
The list of available targets is shown below.
Usage: "Setenv [/Debug | /Release][/x86 | /x64 |
/ia64][/vista | /xp | /2003 | / 2008 /win7 ] [-h or /?]"
/Debug - Create a Debug configuration build environment
/Release - Create a Release configuration build environment
/x86 - Create 32-bit x86 applications
/x64 - Create 64-bit x64 applications
/ia64 - Create 64-bit IA64 applications
/vista - Windows Vista applications
/xp - Create Windows XP SP2 applications
/2003 - Create Windows Server 2003 applications
/2008 - Create Windows Server 2008 or Windows Vista SP1 applications
/win7 - Create Windows 7 applications
By default, the Windows SDK is installed to your local disk in the locations below. The default installation path for most components of this SDK is C:\Program Files\Microsoft SDKs\Windows\v7.0.
The default installation path for the Visual C++ compilers is a different location. On an x86 computer, the default installation path of the Visual C++ compilers is c:\Program Files\Microsoft Visual Studio 9.0\VC. On an x64 or IA64 computer, the default installation path of the Visual C++ compilers is c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC.
Windows SDK tools
Windows SDK documentation
Windows SDK headers
Import libraries and TLB files
Windows SDK license information
Windows SDK samples
This release of the Windows SDK has the following known issues, categorized by type:
The Windows SDK does not set the HKLM\Software\Microsoft\.NETFramework\sdkInstall Rootv2.0 registry key to a string value containing the root directory of the Windows SDK installation. Some MSBuild tasks might expect this registry key to be set. If you already have .NET Framework SDK 2.0 or Microsoft 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 Microsoft Visual Studio 2005, you might receive an error message from MSBuild tasks with a dependency on this key. To workaround this issue set the string value of this key to the root directory of the Windows SDK installation. By default, this directory is C:\Program Files\Microsoft SDKs\Windows\v7.0
Additionally, in order to use AL.exe, the ALToolPath parameter must be set and passed to msbuild (see more in section 5.4.11). For the default install location, you can use the following command:
On an X86 computer:
msbuild /p:ALToolPath="C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
On an X64 or IA64 computer:
msbuild /p:ALToolPath="C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\X64
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. For more information, see the Windows SDK blog post on this issue.
Workaround: follow these instructions to manually edit SetEnv.cmd to remove the second call to REG:
1. Open C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\SetEnv.cmd in Notepad or another editor
2. 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.
3. Save SetEnv.cmd
4. Restart the Windows SDK command prompt
The SDK provides documentation and sample code that targets .NET Compact Framework. However, actual development of .NET Compact Framework applications requires Microsoft Visual Studio 2005 or Visual Studio 2008. When building a sample that depends on .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, install either Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008, or download and install the .NET Framework 2.0 SDK.
If you have Microsoft Visual Studio 2008 installed and then install the Windows SDK, an important registry key is changed. This key points to the SDK tools as well as to Windows Headers and Libraries. However, if you run a custom installation of the Windows SDK that does not include either tools or Headers and Libraries, the link to those files will be broken, and your projects will fail to compile with an error like this one:
LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
To fix this issue, either repair Microsoft Visual Studio 2008 to restore it to its original state or install the tools, headers and libraries from the SDK.
Game Explorer provides an easy, customizable way to present your game to users of Windows Vista. Documentation on using Game Explorer is not included with the Windows SDK. To view this content, visit the MSDN Online Library.
When the Windows SDK is installed to a custom location, the Microsoft Documentation Explorer and the ATL/MFC runtime are not installed by the Windows SDK. These components may already have been installed by other applications, such as Visual Studio or MSDN. If these items have not been installed previously, then documentation will not open and some tools, such as guidgen.exe, will not run.
To workaround this issue:
1. Navigate to <system drive>\Program Files\Microsoft SDKs\Windows\v7.0\Setup\sfx
2. Double-click on dexplore.exe and vcredist.exe to install Microsoft Document Explorer and the ATL/MFC runtime.
The following tools are not included with this release of the Windows SDK. These tools had been in the Windows SDK Vista Update:
· depends.exe (the Dependency Walker tool can be downloaded from http://dependencywalker.com)
CAPICOM.dll has been removed from the Windows SDK. It should be considered a deprecated component. You can find information on alternatives to using CAPICOM here - http://msdn.microsoft.com/en-us/library/cc778518(VS.85).aspx. If you need to use CAPICOM.dll, you can download it separately from http://www.microsoft.com/downloads/details.aspx?FamilyID=860EE43A-A843-462F-ABB5-FF88EA5896F6
The following tools have been added since the M3 release of the Windows SDK:
· Windows Troubleshooting Toolkit
The following tools require .NET Framework 3.5 SP1, which does not ship with the Windows SDK:
The command-line environment for The Windows SDK Version Selection tool supports only Visual Studio 2008. It does not support earlier versions of Visual Studio. See the Windows SDK Blog post about the Windows SDK Configuration Tool for more information about the tool and this issue.
The use of mt.exe to add a manifest resource to a PE image file (.EXE, .DLL, etc.) that does not already contain a resource (.rsrc) section in it may fail on Windows 7 Beta. The problem does not occur on Windows XP, Windows Vista, and Windows Server 2008, nor does it occur on Windows 7 Beta when manipulating PE image files that already contain a resource section.
1. Use mt.exe on Windows XP, Windows Vista or Windows Server 2008 instead of Windows 7 Beta, or
2. If using Windows 7 Beta, use an external manifest file or ensure the PE image has a non-zero length resource section.
External Manifest File:
For .EXE files, the manifest need not be embedded as a resource. Rather, it may simply be placed next to the .EXE. I.e., for ‘hello.exe’, the manifest ‘hello.exe.manifest’, when placed next to it, has the same effect as if the manifest were embedded as a resource. This is true only for .EXE files.
Create a Non-Zero-Length Empty Resource
If it is imperative that mt.exe later be used to embed a manifest, and the PE image file in question cannot otherwise be guaranteed to have a resource section, then an empty resource script may be used. Despite that the script is empty, the resultant resource section will not be zero-length, and mt.exe can then be used. For example:
i. cl.exe /c hello.c
ii. echo. > hello.rc
iii. rc.exe /r hello.rc
iv. link.exe /out:hello.exe hello.obj hello.res
v. mt.exe -outputresource:hello.exe;1 -manifest: hello.exe.manifest
vi. (the file hello.exe now exists with hello.exe.manifest embedded)
To build the samples in the SDK build environment or in Microsoft Visual Studio 2008, you must upgrade many of the Win32 samples project files. The compilers in the SDK are Visual C++ v9.0 SP1, the same compilers that ship in Microsoft Visual Studio 2008 SP1. Many of the sample project files in the SDK are written for VC 8.0 compilers, the compilers that ship in Microsoft Visual Studio 2005. Samples with version 8.0 project files can be built in Microsoft Visual Studio 2005 but must be upgraded before being built in the Windows SDK build environment or in the Visual Studio 2008 or later build environments. When building a project file in the SDK Build environment, you might receive this error:
GramEvcbuild.exe : error VCBLD0010: Project 'foo.vcproj' requires upgrade.
Use 'vcbuild /upgrade' or 'devenv /upgrade' to upgrade the project.
To workaround this issue, follow the prompt in the command window and type vcbuild /upgrade or devenv /upgrade to upgrade the project.
The .NET Framework (managed) sample vcproject files cannot be upgraded using the workaround above. These must be upgraded using vcbuild /upgrade /overrideRefVer "SampleName.vcproj" because upgrade /overriderefver indicates that it will use .NET Framework 3.5.
Some of the samples in the SDK contain v9.0 project files, which will not build in Visual Studio 2005. You cannot downgrade the project files to a lower version. To workaround this issue, install Visual Studio 2008 (Express or Retail SKU) or build the sample in the Windows SDK command line build environment.
Some samples included with the Windows SDK have dependencies on components outside the Windows SDK.
Some samples require the ATL and/or MFC headers, libraries, or runtime, which are included with Visual C++ (non-Express editions). When building a sample that depends on ATL/MFC without Visual Studio installed on your computer, you might see an error similar to this:
fatal error C1083: Cannot open include file: 'afxwin.h': No such file or directory
To workaround this issue, install a non-Express version of Microsoft Visual Studio 2005 or Visual Studio 2008.
The SchemaReader sample requires Windows Media Player 11 or later to be installed.
The samples in the \Samples\SysMgmt\MMC3.0 directory require Microsoft Management Console 3.0 or later to be installed.
Some samples require the DirectX SDK (refer to the sample's readme for additional information).
Some samples fail to build because the file msime.h is not found. Msime.h is not shipped with the Windows SDK. Msime.h is for use by developers when customizing applications for the 2007 Microsoft Office System.
The affected samples are:
To workaround this issue, download msime.h from the Microsoft Download Center and copy to the Windows SDK \Include directory.
A few unmanaged samples rely on mspbase.h, mtyp.h, or mfc80ud.lib. These files are included with Microsoft Visual Studio 2005 and do not ship with Microsoft Visual Studio 2008.
When building a C++ sample that does not have support for x64 on an x64 computer, you might see the following error message:
fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
To workaround this issue, perform one of the following actions:
1. Build the sample targeting x86 by using this code:
vcbuild *.vcproj /platform=win32
2. Add x64 support by doing the following:
a. Load the sample in Microsoft Visual Studio (C++).
b. Update the Configuration Manager under Project | Properties.
For detailed instructions, see the Windows SDK Blog post "How to add 64-bit support to vcproj files."
Note: if you do not install libraries for all CPU architectures during SDK setup, some samples with Visual C++ project files might fail to build with this error for all configurations in the project file:
Fatal error LNK1181: cannot open input file
For example, if a sample has an x86 configuration and x86 libraries were not installed (these libraries are installed by default when installing the SDK on all platforms), the sample will fail to compile.
J# samples will not build using the Windows SDK because there is no appropriate build environment. This edition of the Windows SDK does not support building J# applications. To workaround this issue, install Visual Studio (VJ++) 2005.
The Windows Communication Foundation samples setup script Setupvroot.bat does not work on Windows Vista if the NetMsmqActivator service is enabled and Message Queuing (MSMQ) is not installed. The iisreset utility does not work unless MSMQ is installed or the NetMsmqActivator service is disabled. The WCF samples setup script Setupvroot.bat will not run unless MSMQ is installed or the NetMsmqActivator service is disabled.
Make sure MSMQ is installed or disable the NetMsmqActivator service on Windows Vista before you run the WCF samples setup script Setupvroot.bat.
Some samples might fail to compile on all platforms 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 want to build for:
Msbuild *.sln /p:platform=Win32
Msbuild *.sln /p:platform=x64
VCbuild *.vcproj /platform:Win32
VCbuild *.vcproj /platform:x64
.NET Compact Framework samples in the Windows SDK will not compile without .targets files installed on your local disk atC:\Windows\Microsoft.NET\Framework\<version>\Microsoft.CompactFramework.<language>.targets
To workaround this issue, install either Visual Studio 2005 or 2008 to install the .targets files.
The affected samples are:
The Windows SDK Win32 sample WinUI\Speech\Tutorial fails to compile, generating the following error:
error PRJ0019: A tool returned an error code from "Performing Custom Build Step".
Issue: a Custom Build Step in the VC project files incorrectly references the GC.EXE tool (speech engine) with a relative path.
To workaround this issue, edit each of the sample’s .vcproj files, removing ..\..\..\bin\ at the start of the command-line for any "Grammars" files.
When building a .NET Framework 3.0 or 3.5 sample in the SDK build environment, Al.exe is not found. (The ALTOOLPATH variable is set by Visual Studio 2005 to point to the .NET Framework 2.0 SDK, included with Visual Studio 2005.) You might receive this error:
Could not locate the .NET Framework SDK. The task is looking for the path t o the .NET Framework SDK at the location specified in the SDKInstallRootv2.0 value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework. You may be able to solve the problem by doing one of the following: 1. ) Install the .NET Framework SDK. 2.) Manually set the above registry key to the correct location.
To workaround this issue, set the ALTOOLPATH environment variable to point to the version of Al.exe that ships in this Windows SDK. You can set ALTOOLPATH for an individual session using the Set command, or set the environment variable permanently at Start Control Panel System. On the Advanced tab, click the Environment Variables button. In the System variables area, click New. Add the variable name ALTOOLPATH with a Variable Value of one of the following:
· For X86 computers: C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
· For x64 computers: C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\x64
· For IA64 computers: C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\IA64
The “Playlistparser” and “Authorization” plug-in samples should be available in Windows Media Services. The user should be able to enable and disable the newly built plug-ins. However, the “Playlistparser” and “Authorization” plug-ins fail to build and produce the following error:
Syntax error for the code given below in Unknwn.idl
[in] REFIID riid,
[out, iid_is(riid), annotation("__RPC__deref_out")] void **ppvObject);
To workaround this issue, build the “Playlistparser” and “Authorization” plug-ins on Windows Vista or Windows 2003 Server and copy the plug-ins to Windows 2008 Server.
The XPS Rollup code sample that installs to \samples\XPS\XpsRollup does not compile. A working updated version of the sample code can be found on Code Gallery: "http://go.microsoft.com/fwlink/?LinkId=136633".
When installing the SDK, users are given the option of deselecting certain components. It is possible to deselect the Documentation/.NET Framework component, while leaving the Samples/.NET Framework/Samples in Documentation selected. When this specific combination is chosen, the .NET Framework Samples will fail to install correctly and an installation error will be generated in the SDK Installation Log. If a user attempts to correct this issue by running the Change wizard in Programs and Features (Add Remove Programs on pre-Vista operating systems), the .NET Framework Documents will install correctly but the samples will still be missing.
Access the .NET Framework samples directly opening the managed sample .zip files installed by default to \Program Files\Microsoft SDKs\Windows\7.0\Samples.
Workaround 2: Repair the SDK Installation
The Windows SDK is provided as-is and is not supported by Microsoft. For technical support, there are a number of options:
Microsoft Professional Support for Developers provides incident-based access to Microsoft support professionals and rich information services to help developers to create and enhance their software solutions with Microsoft products and technologies.
For more information about Professional Support for Developers, or to purchase Professional Support incidents, please contact a Customer Representative at 1-800-936-3500. To access Professional Support for Developers, visit the MSDN Web site. If you have already purchased support incidents and would like to speak directly with a Microsoft support professional, call 1-800-936-5800.
MSDN Online provides Developer Support search, support incident submission, support highlights, service packs, downloads, technical articles, API information, blogs, newsgroups, forums, webcasts, and other resources to help optimize development.
Your feedback is important to us. Your participation and feedback through the locations listed below is appreciated.
· The MSDN Forums are available for peer-to-peer support.
· Windows SDK Developer Center is the official site about development using the Windows SDK, and provides information about the SDKs, links to the Windows SDK Blog, Forum, online release notes and other resources.
· The Windows SDK Forum deals with topics related specifically to the Windows SDK.
· The Software Development for Windows Vista forum contains an updated list of related forums.
· You can also send mail to the Windows SDK Feedback alias at firstname.lastname@example.org.
· The Windows SDK Blog contains workarounds, late-breaking and forward-looking news.
Copyright © 2008 Microsoft Corporation. All rights reserved. Legal Notices: http://www.microsoft.com/legal/.