Welcome to the Microsoft® Windows® Software Development Kit (SDK) for June Community Technology Preview (CTP). The Windows SDK contains documentation, samples, headers, libraries, and tools designed to help you develop Microsoft® Windows applications. The documentation, samples, and tools provided in the Windows SDK support application programming interfaces (APIs) available in the Windows Vista™, Microsoft® Windows® XP Service Pack 2 (SP2), and Microsoft® Windows® Server 2003 Service Pack 1 (SP1) versions of Windows.
Important This version of the Windows SDK is available as both a DVD ISO image that must be burned to a DVD or mounted as a virtual drive and installed from that media, and as a web download.
Note The DVD ISO image requires a minimum of 1.5 GB of free disk space to install. If you do not have the much free disk space, you can use the SDK's custom setup options to install a subset of the content.
Important This version of the Windows SDK targets specific versions of Windows and has other restrictions. This version:
Important 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.
Please note that this release is for preview purposes only. The APIs, documentation, samples, headers, libraries, and tools provided in this release are preliminary and subject to change.
Important When building samples, do so in a directory outside of Program Files to which you have write access. For more information, see the Samples section below.
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 pre-release of the Windows SDK supports the RTM release of Microsoft® Visual Studio® 2005. You can download a copy at no charge from the Visual Studio 2005 Developer Center
.This pre-release of the Windows SDK supports x86, x64, and IA64 platforms for building and running samples.
By default, the Windows SDK is installed to your hard disk in the locations described in the following table. This list is not complete, but covers the most common directories.
Directory
Contents
\Bin
Windows SDK tools
\Help
Windows SDK documentation
\Include Windows SDK headers \Lib
Import libraries and TLB files
\License
Windows SDK license information
\Samples
Windows SDK samples
Please install on a clean machine or completely uninstall any pre-releases of the Microsoft® WinFX® Runtime Components 3.0, the WinFX SDK, the Platform SDK, the Windows SDK, the .NET Framework redistributable, Microsoft® Visual Studio®, and their dependencies before installing this release. These older components may interfere with this release, causing setup to fail or break functionality. We recommend installing this version on non-production machines (preferably in a test environment) without these previous releases to prevent incompatibilities.
To install on Microsoft Windows XP Service Pack 2 or Microsoft Windows 2003 Server Service Pack 1:
To install on Windows Vista:
Download the Windows SDK as described in Steps 2 through 6 above. The .NET Framework 3.0 is available by default in Windows Vista.
Note If you intend to use Visual Studio to develop .NET Framework 3.0 applications, you must install the Windows SDK before installing the Visual Studio 2005 Extensions for .NET Framework 3.0. It is essential that you use the version of Visual Studio identified in the Installation Instructions in .NET Framework 3.0 setup.
Access the Windows SDK through the Start menu at Microsoft Windows SDK. The Start menu folder contains pointers to the documentation (which contains the samples for .NET Framework 3.0), tools, and debug and release build environments. Documentation for the Windows SDK is also available on MSDN Online at http//windowssdk.msdn.microsoft.com/library.
This release has the following known issues. Known issues are categorized by content type.
6.1 Setup and General Development
6.1.1 Windows SDK disk space requirements
The complete DVD ISO installation of the Windows SDK requires 1.5 GB or more disk space to successfully install. Please verify that the machine you're 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.
6.1.2 Several SDK components must be uninstalled separately in Add/Remove Programs
The Windows SDK installs both its core components and external applications as separate MSI files. Please note that several applications will need to be uninstalled from Add/Remove Programs in order to fully remove all SDK components. Those components are:
Due to SDK componentization, for we recommend re-running the SDK setup.exe from your download location and choosing which features to install. For example, if you choose "Microsoft Windows Software Development Kit" from Add/Remove Programs and then "Change," you'll see a different screen that doesn't show all the internal and external content installed as MSI files.
If you originally just installed the x86 development environment and now want to install the x64 development environment, you need to relaunch the SDK setup.exe versus launching the "Change" functionality for the "Microsoft Windows Software Development Kit" located in Add/Remove Programs in the Control Panel.
6.1.3 VSS Software Provider ID is required to use some APIs
The VSS Software Provider ID is needed to use various APIs, including the shadow copy storage management interfaces (IVSSSnapshotMgmt).
To add this provider ID, define a const GUID and use that in your code.
// {b5946137-7b9f-4925-af80-51abd60b20d5}
static const GUID VSS_SWPRV_ProviderID =
{ 0xb5946137, 0x7b9f, 0x4925, { 0xaf, 0x80, 0x51, 0xab, 0xd6, 0x0b, 0x20, 0xd5 } };
In a few cases, you may need to use the Software Provider GUID to access some APIs (GetProviderMgmtInterface method on the IVSSSnapshotMgmt interface.
The GUID can also be obtained by vssadmin list providers. Alternatively, you can use the definition listed above your sources.
6.1.4 Known issues with Windows Workflow Foundation (WF)
There are a few known issues with Windows Workflow Foundation (WF) in this SDK release. See the online Windows Workflow Foundation Runtime Components Readme for a complete list.
6.1.5 Visual Studio 2005 is required for .NET Compact Framework development
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.
6.1.6 Windows Presentation Foundation Imaging Component does not support metadata that spans multiple APP segments
JPEG APP headers do not support metadata segments larger than 64K. The Windows Presentation Foundation Imaging Component does not support metadata that spans multiple APP segments. If you add a color profile larger than 64K to the APP2 metadata marker of a JPEG image, the color profile may become corrupt if the image or the metadata are modified.
There is no workaround for this issue.
6.2 Headers and Libraries
This section describes known issues with headers and libraries included in the Windows SDK and offers possible workarounds.
6.2.1 Using the Windows SDK to develop Win32 C++ applications with Visual Studio 2005
In order to utilize Windows SDK headers, libraries, and tools within Visual Studio 2005, the SDK-provided Visual Stuido registration tool must first be run. When running this tool on a Windows Vista machine it must be run for each user.
To run the Visual Studio Registration Tool, go to
Start --> All Programs --> Microsoft Windows SDK --> Visual Studio Registration--> Register Windows SDK Directories with Visual Studio 2005.
6.3 Compilers
The following section describes known issues with compilers and offers possible workarounds.
6.3.1 The J# Compiler is not available in this version of the Windows SDK
J# samples will not build using the Windows SDK because there is no appropriate build environment.
There is no workaround. This edition of the Windows SDK does not support building J# applications.
6.3.2 Debugging Windows Presentation Foundation (WPF) applications with Kernel Debugger Active may result in an error
When debugging WPF applications, the following error message may appear:
Debugging isn't possible because a kernel debugger is enabled on the system.
This message occurs while debugging managed code on a system running Windows® NT, Windows® 2000, or Windows XP that has been started in debug mode.
6.4 SDK Tools
This section describes known issues with Windows SDK tools and possible workarounds.
6.4.1 Tb3x.exe has been deprecated and removed from the Windows SDK
Tb3x.exe has been deprecated and removed from the Windows SDK. There is no known workaround for this issue.
6.4.2 The Application Verifier tool is not available in the Windows SDK
The Application Verifier tool is not available in the Windows SDK. It ships as part of the Windows Application Compatibility Toolkit.
To work around this issue, download the Windows Application Compatibility Toolkit from Download Center.
6.4.3 UISpy.exe fails to run and displays a strong name validation error
UISpy sometimes fails to run and displays a strong name validation error.
This error occurs because UISpy.exe was delay signed and never resigned. By default, this causes the .NET runtime to fail the execution of UISpy.exe because the strong name signature in the executable is not valid. However, UISpy will run correctly if you configure the runtime to ignore the strong name signature for UISpy.exe.
To work around this issue, register UISpy.exe for strong name verification skipping.
1. Open a Windows SDK command prompt.
2. Navigate to the /bin directory. By default, this is C:\Program Files\Microsoft SDKs\Windows\v1.0\bin.
3. Run the command SN -Vr UiSpy.exe. Example
C:\Program Files\Microsoft SDKs\Windows\v1.0\Bin>sn -Vr UiSpy.exe
The successfully run command will produce a message indicating that the verification entry was added for the UISpy assembly.
6.4.4 Svcutil.exe Fails to Generate Configuration File for Queued Sessions and Queued Volatile Samples
When using queued sessions and queued volatile samples, running svcutil.exe generates the following warning:
“Warning Unable to
import wsdlbinding”
Svcutil.exe also fails to generate a configuration file in this case.
There is no workaround for this issue. This issue will be addressed in a future release.
6.4.6 Previous versions of Windows PowerShell must be Uninstalled
If you intend to install Windows PowerShell, please uninstall any previous versions of Monad. The Windows SDK setup will not prompt you to uninstall Monad prior to installing Windows PowerShell.
6.4.7 Windows PowerShell Release Notes are available in separate download
In addition to shipping in the Windows SDK, Windows PowerShell (formerly code-named "Monad"), a new task-based command line shell and scripting language for system administration, is now available for download for x86, x64, and IA64 platforms.
The download contains the Windows PowerShell binaries as well as Release Notes, which do not ship separately in the Windows SDK.
6.4.8 Windows PowerShell Not Integrated for SDK Application Development
Windows PowerShell in this release of the Windows SDK does not fully support command line development because the location Windows SDK headers, libraries, tools, and reference assemblies are not properly set for use by Windows PowerShell.
6.5 Samples
This section describes known issues with Windows SDK samples and possible workarounds.
Note Some .NET Framework 3.0 samples have specific dependencies or setup requirements. If you find that a sample in the samples .zip files is not working properly, first check the sample page in the documentation for instructions.
6.5.1 Building Samples from a directory other than the Sample Directory
When building Samples, do so in a directory outside of Program Files to which you have write access. To build from the command line:
1. Open either the CMD Shell or PowerShell command prompt.
2. Copy the sample to a working folder not under Program Files. Copying to a location other than Program Files makes it possible to maintain a pristine copy of the samples installed by the SDK as well as avoid issues when writing to files and directories located under Program Files.
3. Build the sample from the command line as follows:
Build a makefile by typing nmake.
- msbuild mysample.csproj.
Build a .csproj file by typing
Build a .vbproj file by typing msbuild mysample.vbproj.
Build a .vcproj by typing vcbuild mysample.vcproj.
6.5.2 Not All C++ Samples with Visual C++ 2005 Project Files have Configurations for X64
Not all samples with Visual C++ 2005 project files have configurations to build for X64. To workaround this just load the sample in Visual C++ 2005 and update Configuration Manager under Project | Properties. Additionally, if you do not install libraries for all CPU architectures, some samples with Visual C++ 2005 project files may fail to build (link fails with "fatal error LNK1181: cannot open input file") for all configurations in the project file. For example, if a sample has an x86 configuration and no x86 libraries were installed (the default install setting when installing the SDK on a X64 machine), that sample's x86 configuration will fail to build.
6.5.3 Where to Find .NET Framework 3.0 Samples
Samples demonstrating .NET Framework 3.0 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 3.0 samples can be accessed in bulk by directly opening the sample .zip files located in %MSSDK%\Samples.
6.5.4 The following .NET Framework 3.0 samples do not compile in this version of the Windows SDK
The samples listed below do not compile in this version of the SDK. There is no known workaround for this issue.
6.5.5 Building an Application with the SDK and ATL or MFC
The following samples require Visual Studio 2005 to build either because an ATL or MFC header is required that Visual Studio 2005 ships.
The SDK does not come with either ATL or MFC headers, libraries, or runtimes. However, if you have Visual C++ 2005 (non-Express editions) installed on your system, you can use the SDK to build using ATL or MFC.
1. Open an SDK command window.
2. Type cd %MSSDK%\Setup.
3. Run VCIntegrate.exe.
4. From this point forward, command windows will now have the proper environment settings to build an application that takes advantage of the SDK.
Note If you want to disable support, run VCIntegrate /u to uninstall changes and return to command windows with no ATL or MFC support.
The following samples require an ATL or MFC header that Visual Studio 2005 ships, but the Windows SDK does not ship.
6.5.6 Must Install Peer Networking Feature on Microsoft Windows XP SP2 Before Running WCF Peer Channel Samples
The documentation for three of the WCF samples is missing instructions on how to install the Peer Name Resolution Protocol (PNRP) on a computer running Windows XP SP2. These samples are:
Net Peer TCP Sample
Peer Channel Secure Chat Sample
Peer Channel Custom Authentication Sample
To install PNRP on Windows XP SP2 (one-time setup):
1. In Control Panel, double click Add or Remove Programs.
2. In the Add or Remove Programs dialog box, click Add/Remove Windows Components.
3. In the Windows Components Wizard, select the Networking Services check box, and then click Details.
4. Check the Peer-to-Peer check box and click OK.
5. Click Next in the Windows Components Wizard.
6. When installation completes, click Finish.
7. From a command shell, start the PNRP service using the following command
net start pnrpsvc
6.5.7 Some NetDS/Peer to Peer samples need to be run from a non-elevated window
The following samples cannot be run from an elevated window:
- Contacts
- Invitation
- People Near Me
To work around this issue, run these applications from a non-elevated window.
6.5.8 SideShow samples build on Windows Vista only
The Alarms, HelloWorld, Pictures, and Tasks SideShow samples are Windows Vista-specific. While the makefiles for these samples will allow a build to start when targeting previous versions of the operating system, the samples will not build successfully.
6.5.9 Run error in Windows Presentation Foundation Blackjack demo sample
The Windows Presentation Foundation Blackjack demo sample has a known platform animation issue. When a card is drawn for either the player or the dealer, it may end up being placed on the source deck, rather than the player’s or dealer’s deck ~10% of the time. There is no workaround.
6.5.10 Need to Change Visual Studio 2005 Project Files
When building in Visual Studio 2005, the project files for the following .NET Framework 3.0 samples only support building for Win32 | Debug only after you actively select that configuration. The other configurations do not correctly build.
- BEREncoding
- Dsml_BatchRequest
- Dsml_Exceptions
- Dsml_PagedSearch
- Dsml_ReadRootDSE
- Dsml_SendRequest
- Ldap_AsyncSend
- Ldap_Exceptions
- Ldap_PagedSearch
- Ldap_PrintDomain
- Ldap_ReadRootDSE
- Ldap_Referral
- Ldap_SendRequest
6.5.11 The SchemaReader sample requires Windows Media Player 11
The Windows Media Player SchemaReader sample requires Windows Media Player 11 to be installed.
6.5.12 Digital Signal Processing (DSP) plug-ins created by the Windows Media Player plug-in wizard might not work with Windows Media Player 11
Digital signal processing (DSP) plug-ins created using the Windows Media Player plug-in wizard are single-threaded. This release of Windows Media Player 11 requires that DSP plug-ins be multi-threaded. Attempting to load a single-threaded DSP plug-in into Windows Media Player 11 may yield unexpected results.
Microsoft is aware of this issue and is working to provide support for existing single-threaded DSP plug-ins in future releases of Windows Media Player 11.
6.5.13 MMC 3.0 samples requires that MMC 3.0 is installed
When the Windows SDK is installed on an x86 Windows Server 2003 SP1 machine, MMC 3.0 samples do not compile. To work around this issue, install MMC 3.0 components.
6.5.14 The Security Certificate Services Ocspsample does not build on or for Windows Vista
There is no workaround for this issue.
6.5.15 The following Windows Media 9 samples require additional steps to build
The following samples require additional steps to build:
To build the Logging and CacheProxy samples:
6.5.16 The IPConfig sample crashes
When running the \Samples\NetDS\IPHelp\IPConfig sample, it crashes trying to display the DHCP lease data.
To work around this issue, either comment out or update the usage of the gmtime and asctime APIs ipconfig.cpp. Specifically, update the following lines:
// Display coordinated universal time - GMT
//newtime = gmtime(&pAdapt->LeaseObtained);
//printf( "\tLease Obtained. . . . . . . %s", asctime( newtime ) );
//newtime = gmtime(&pAdapt->LeaseExpires);
//printf( "\tLease Expires . . . . . . . %s", asctime( newtime ) );
6.6
Documentation6.6.1 Some links are broken in the SDK documentation
Some links in the Class Library and other areas of SDK documentation are broken. These will be fixed in future releases. There is no workaround for this issue.
6.6.2 No “How Do I” articles are available from the Windows SDK documentation viewer
How Do I pages will be available in a future pre-release. There is no workaround for this issue.
6.6.3 Some in-page language filter options may filter out required syntax blocks in WPF reference pages
In some cases, both XAML and either C# or VB code are required to successfully build and run samples. Applying either the C#, VB, or XAML filters alone may exclude necessary syntax from the page view. This is currently by design, and the design may be revisited in a later release.
6.6.4 In some cases, some filters may not work as expected
In some cases, filters may not work as expected. This is a known issue and will be fixed in a future release.
The pre-release Windows SDK is provided "as-is" and is not supported by Microsoft. If you have questions or need assistance, several newsgroups are available to help you.
If you have questions or need assistance, see The MSDN Online Windows Vista Developer Center and the Windows Vista Beta Newsgroups for additional information and updates to the known issues.Your feedback is important to us. Your participation and feedback through the Windows Vista Beta Newsgroups is appreciated.
Copyright © 2006 Microsoft Corporation. All rights reserved. Legal Notices.