Windows SDK Release Notes
1. Welcome
Welcome to the Windows® Software Development Kit (SDK) for Windows Vista™.
The Windows SDK contains documentation, samples, headers, libraries, and tools designed
to help you develop Windows applications. The documentation, samples, and tools
provided in the Windows SDK support application programming interfaces (APIs) available
in the Windows Vista, Windows XP Service Pack 2 (SP2), and Microsoft Windows Server
2003 Service Pack 1 (SP1) versions of Windows. Not all APIs are supported on all platforms.
See the specific API documentation to determine which platform the API supports.
Related Tools
There are a number of related tools to make your experience with the Windows SDK better:
-
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.
-
The Microsoft .NET Framework 3.0
(formerly WinFX), is the new managed
code programming model for Windows. 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").
-
LUA Buglight™ is a tool to help both developers and IT Pros (sysadmins) identify
the specific causes of admin-permissions issues (a.k.a., “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.
- The Microsoft Data Access Components (MDAC) SDK
is for developers who are building applications using ADO, OLE DB, and ODBC.
It contains updated documentation, headers, libs and typelibs for x86, IA64 and AMD64 platforms,
as well as updated sample applications and developer tools. The MDAC 2.8 SDK is designed for use with the
MDAC redistributable.
2. License Agreement
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.
3. Supported Compiler, Platforms and Related Software
This release of the Windows SDK supports the RTM release of Microsoft ®
Visual Studio ®2005. 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, and x64 platforms for building and
running samples. The IA64 platform is not supported in this release.
4. Downloading and Installing
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.
4.1 Downloading
This version of the Windows SDK is available in two versions: a DVD ISO image, and
as a web download.
The DVD ISO image of the Windows SDK available from Download Center will not install
the SDK directly on to your hard disk without the use of additional tools. See the
Installation Instructions below for more information. The DVD ISO image requires
a minimum of 1.4 GB of free disk space to install. If you do not have that much
free disk space, you can use the SDK's custom setup options to install a subset
of the content.
The web download is also available from the Download Center. The web download will
stream the SDK content to your local machine.
4.2 Installation
It is recommended that you uninstall all previous prerelease versions of the Windows SDK
prior to installing this version of the SDK. Note that you may see more than one Windows
SDK product listed in the Upgrade Options screen. All of the Windows SDK products may be
removed by going to Add/Remove Programs, browsing for the Microsoft Windows Software Development
Kit, and selecting Remove (in Windows XPSP2 and Windows Server 2003) or Uninstall (in Windows Vista).
Please install on a clean machine or completely uninstall any pre-releases
of the 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.
To install on Microsoft Windows XP Service Pack 2 or Microsoft Windows 2003 Server
Service Pack 1:
- If you intend to install the .NET Framework 3.0 components available in the Windows
SDK, install the .NET Framework 3.0 from the Download Center.
- If you created a DVD ISO image or mounted a virtual drive and launch setup.exe, choose
the appropriate option to install the Windows SDK: insert the SDK DVD into a DVD-ROM
drive and click setup.exe, or after the virtual drive is mounted, launch the setup.exe
from within that virtual drive.
- Follow the instructions in the Windows SDK Setup wizard.
-
Optional: Install Microsoft Visual Studio 2005.
-
Optional: Install the Visual Studio 2005 Extensions for .NET Framework 3.0
from the Download Center.
-
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, debug and release build environments. Documentation
for the Windows SDK is also available on MSDN Online at http//windowssdk.msdn.microsoft.com/library.
To install on Windows Vista, step 1 in not necessary. 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.
4.3
Building Samples
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.
4.4
File System Layout
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
|
4.5
Other Tools and Download
5. Known Issues
This release has the following known issues. Known issues are categorized by content
type.
5.1 Setup and General Development
5.1.1
Windows SDK Disk Space Requirements
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.
5.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 remove all SDK components. Those components are:
- Debugging Tools for Windows
- Microsoft Windows Software Development Kit
- Microsoft .NET Compact Framework 2.0
- Microsoft FxCop 1.3.5
- Microsoft Document Explorer
Note that you may have installed some of these applications outside of your SDK
installation. Removing those applications from Add/Remove Programs will make those
applications unavailable for other applications that may use them.
Due to SDK componentization, 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 will see a different screen that does not show all the internal and external
content installed as MSI files.
If you originally only 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.
5.1.3
Running Change or Repair on Setup from Add/Remove Programs Fails
If the SDK was installed from a networked drive as a regular user, the Change or Repair
functionality from the Maintenance screen in Add/Remove Programs will fail.
To work around this issue, re-launch setup.exe
from the networked drive.
This will lauch the Mainenance screen, from which the installation can be changed
or repaired.
5.1.4
Uninstalling the Windows SDK for Windows Vista when Visual Studio 2008 is also installed removes registry keys required by Visual Studio 2008
If you have installed either the Windows SDK for Windows Vista or the Windows SDK Update for Windows Vista along with Visual Studio 2008, and then uninstall the Windows SDK, registry keys are removed that Visual Studio requires to find Windows SDK headers, libraries and tools.
To work around this problem, do one of the following things:
- Repair Visual Studio 2008 from Add/Remove Programs (on Windows Server 2003 and Windows XP) or from Programs and Features (on Windows Vista and Windows Server 2008).
- Install the forthcoming Windows SDK for Windows Server 2008 and .NET Framework 3.5.
5.1.5
VCIntegrate doesn't update include
, lib
or bin
paths in Visual Studio
Visual Studio needs to be run at least once before VCIntegrate is run.
After installing Visual Studio, run Visual Studio, then run VCIntegrate.
5.1.6
Running VCIntegrate fails in Windows Vista
In Windows Vista, running VCIntegtrate fails with the error "Unable to access the required files".
This because VCIntegrate needs to be run with elevated privileges. To do this, from the "Start" menu,
navigate to "Microsoft Windows SDK->Visual Studio Integration" and right-click on
"Integrate Windows SDK with Visual Studio 2005" and select "run as administrator".
Alternatively, open a build environment as administrator, and run VCIntegrate from there.
5.1.7
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.
5.1.8
Build tools fail on x64
Make sure the x64 tools are being used, and not the x86 tools. The x64 tools are located
in "Program Files" directory and the x86 tools are located in the "Program Files (x86)" directory.
5.1.9
Running SETENV.CMD from a CMD windows fails
SETENV.CMD requires that both command extensions and environment variable expansion be turned on.
Either use the "CMD Shell" shortcut installed with the Windows SDK or ensure that CMD
is launch with the /V:ON and /E:ON parameters. For example, CMD \V:ON \E:ON
.
5.1.10
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.
Vssadmin list providers can also obtain the GUID.
5.1.11
Volume Shadow Copy Service tools and samples can't be found
Volume Shadow Copy Service tools are located in bin\vsstools
(or bin\x64\vsstools
and bin\ia64\vsstools
for the x64 and ia64 version, respectively) and the corresponding samples are
in samples\winbase\vss
.
5.1.12
Pausing and Resuming an Animation Does Not Work as Expected when DesiredFrameRate
is Set
Timeline
objects with a DesiredFrameRate
value other than a null reference (Nothing in Visual Basic)
do not pause and resume as expected.
5.1.13
An InvalidCastException
occurs when clicking on a ListBoxItem/ComboBoxItem/TabItem after animating SelectedIndex
Clicking on a ListBoxItem, ComboBoxItem, or TabItem after animating the SelectedIndex
property of
its ListBox, ComboBox, or TabControl container throws an InvalidOperationException
.
5.1.14 Performance Impacts of HandoffBehavior.Compose
When you apply an animation to a property using the Compose HandoffBehavior, any clocks objects
previously associated with that property continue to consume system resources; the timing system
will not remove these clocks automatically.
To avoid performance issues when you apply a large number of clocks using HandofffBehavior.Compose
,
you should remove composing clocks from the animated property after they complete. There are several ways to
remove a clock.
- To remove all clocks from a property, use the
ApplyAnimationClock
or BeginAnimation
method of the animation object. Specify the property being animated as the first parameter, and a null reference
(Nothing in Visual Basic) as the second. This will remove all animation clocks from the property.
- To remove a specific
AnimationClock
from a list of clocks, use the Controller
property of the AnimationClock
to retrieve a ClockController
, then call the
ClockController.Remove()
method of the ClockController
. This is typically done
in the Completed
event handler for a clock. Note that only root clocks can be controlled by
a ClockController
; the Controller
property of a child Clock
will return
a null reference (Nothing in Visual Basic). Note also that the Completed
event will not be called
if the effective duration of the clock is forever. In that case, the user will need to determine when to
call ClockController.Remove()
.
This is primarily an issue for animations on objects that have a long lifetime. When an object is garbage
collected, its clocks will also be disconnected and garbage collected.
5.2 Build Environment
The following section describes and offers possible workarounds for known issues
with compilers and known issues with headers and libraries included in the Windows
SDK.
5.2.1
Headers and Libraries: 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 Studio registration tool must first be run. The Visual
Studio registration tool must run in elevated administrator mode on a Windows Vista
computer. 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.
5.2.2
Compilers: 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.
5.2.3
Compilers: 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 is not 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.
5.2.4
Msbuild Reports a Dependency upon the Microsoft .NET Framework SDK 2.0
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 set 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.
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.0
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.0\Bin"
5.2.5
Building files that use DirectX fails
Some header files (including d3dtypes.h, d3drmdef.h and d3d.h) rely on files installed with the DirectX SDK.
To build with these files, the
DirectX SDK must be installed.
5.2.6
The build environment for x64 does not point to the 64bit framework directory.
The build environment for x64 does not point to the 64bit framework directory.
To correct this, 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
You will need administrator privileges to perform this. Using this method, invoking SetEnv.cmd
with the /x86 parameter will cause the build environment to use the x86 frameworks. Otherwise,
the x64 frameworks will be used.
5.3 Documentation
5.3.1
“How Do I” Articles Are Not Available From The Windows SDK Documentation Viewer
The How Do I
feature might be removed in a future release. There is no workaround
for this issue.
5.3.2
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.
5.4 SDK Tools
This section describes known issues with Windows SDK tools and possible workarounds.
5.4.1
Windows PowerShell Can Be Downloaded Directly
Windows PowerShell was available to customers and partners as a part of the Windows
SDK. This is no longer the case. Now, Windows PowerShell can be downloaded directly.
More information on Windows PowerShell is available from the
PowerShell Team Blog
and the Windows PowerShell Technology Center.
5.4.2
The TAPI Browser (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.
5.4.3
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.
5.4.5
The Configuration Editor Tool (SvcConfigEditor.exe) Reloads the Config File When It Is Changed by Another
Entity
If you’re using SvcConfigEditor.exe to edit a config file and another process or
editor accesses that file, SvcConfigEditor.exe will automatically reload the file.
For example, this can happen when anti-virus software scans the config file. The
reload will cause you to lose any changes made to the config file since SvcConfigEditor.exe
last saved it.
To work around this issue, make sure SvcConfigEditor.exe is the only process that
accesses the file during a session.
5.4.5
Possible Application Exception after Removing localIssuer Address Using The Configuration
Editor Tool (SvcConfigEditor.exe)
If you use SvcConfigEditor.exe to delete the address value in the localIssuer element
of clientCredential in the WCF Endpoint Behavior, the tool will create an invalid
configuration file and your application will throw an exception. This is because
SvcConfigEditor.exe doesn’t remove localIssuer when the localIssuer value is an
empty string (an unexpected value).
To work around this issue, manually remove the localIssuer element using some other
editor, such as Notepad.
5.4.6
The TraceViewer Tool (SvcTraceViewer.exe) Does Not Display Arabic Characters Correctly
In traces that contain Arabic characters, the XML view in SvcTraceViewer.exe may
render the characters in reverse order.
To work around this issue use the Formatted View, which displays the traces in the
correct character order. You can also copy the text from the XML view and paste
it into some other editor that displays the characters in the correct order.
5.4.7
Code Generation Language Support in Service Model Metadata Utility Tool (SvcUtil.exe)
SvcUtil.exe can generate code for web service proxies and data types from metadata
in any language that has a managed code provider. SvcUtil.exe has been tested with
the C#, Visual Basic, and C++ managed code providers. Other code providers have
not been tested and may generate code that does not compile or may be otherwise
unusable.
5.4.8 Service Model Metadata Utility Tool (SvcUtil.exe) Can Throw InvalidChannelBindingException When Importing WSDL from Certain Endpoints
While WCF allows setting the ReliableSession’s Binding Element InactivityTimeout
or AcknowledgementInterval properties to TimeSpan.MaxValue, WCF will not consume
WSDL generated by an endpoint with such settings. Instead, the import will fail
and SvcUtil.exe will throw an InvalidChannelBindingException.
To work around this issue, after downloading the WSDL, manually change the TimeSpan.MaxValue
to 2147483647 (Int32.MaxValue). Then, in the generated configuration file, change
the inactivityTimeout or acknowledgementInterval attribute from “24.20:31:23.6470000”
to “Infinite”.
5.4.9 Managed C++ Code Generated Using Service Model Metadata Utility Tool (SvcUtil.exe) Tool May Not Compile
You can use the SvcUtil.exe tool to generate code for web service proxies and data types from metadata.
However, there are known issues with the C++ code provider in Visual Studio 2005 and the .NET Framework
2.0 SDK that can cause the tool to generate Managed C++ code that may not compile. These issues
with the C++ code provider will be addressed in a future release of Visual Studio 2005.
5.4.10 Code Generation Language Support in Service Model Metadata Utility Tool (SvcUtil.exe)
Svcutil.exe can generate code for web service proxies and data types from metadata
in any language that has a managed code provider. Svcutil has been tested with the C#, VB, and C++
managed code providers. Other code providers have not been tested and may generate code that does
not compile or may be otherwise unusable.
5.4.11 Service Model Metadata Utility Tool (SvcUtil.exe) Can’t Generate Data Contracts from a Running Service
An example at the end of the svcutil.exe help output indicates that you can use
the /dataContractOnly (/dconly) option to generate Data Contracts from a running
service:
svcutil /dconly http://service/metadataEndpoint
- Generate Data Contract types from a running service or online metadata documents.
This usage does not work. You can only use the /dconly option to generate Data Contracts
from local metadata files.
5.4.12 MSBuild will use the build tools shipped with Visual Studio (for example, VCBuild) even when used from the Windows SDK build environment
If Visual Studio is installed, MSBuild is hard coded to use the tools installed with Visual Studio.
These may not be the latest versions. To ensure the latest tools installed by the Windows SDK
are being used, use the tools located in the Bin directory of the Windows SDK install
directory (by default, C:\Program Files\Microsoft SDKs\Windows\v6.0 ).
5.4.15 Undecoded WCF traces appear on Windows Vista
On Windows Vista, some ETW providers use manifests instead of MOF registrations.
For such providers without the trace schema in the WMI catalog, the current
version of SvcTraceViewer.exe cannot decode the trace output.
To decode Windows Vista-specific binary traces with no CIM schema,
use the command-line tool TraceRpt.exe, which ships with Windows
Vista.
5.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.
5.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:
- 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.
- Open either the CMD Shell or PowerShell command prompt.
-
Build the sample from the command line as follows:
-
Build a makefile by typing nmake.
-
Build a .csproj file by typing msbuild mysample.csproj.
-
Build a .vbproj file by typing msbuild mysample.vbproj.
-
Build a .vcproj by typing vcbuild mysample.vcproj.
5.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 work around this issue, 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.
5.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.
5.5.4
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 with,
but the Windows SDK does not ship with.
- \com\administration\explore.vc
- \multimedia\audio\aecmicarray
- \multimedia\audio\multichan\
- \multimedia\gameux
- \multimedia\gdi\icm\devicemodelplugin
- \multimedia\gdi\icm\gamutmapmodelplugin
- \multimedia\wia\getimage
- \multimedia\windowsmediaservices9\authentication
- \multimedia\windowsmediaservices9\cacheproxy\cplusplus
- \multimedia\windowsmediaservices9\datasource
- \multimedia\windowsmediaservices9\eventnotification
- \multimedia\windowsmediaservices9\playlist
- \multimedia\wpd\wpdapisample
- \netds\adsi\samples\activedir\propsheethost\
- \netds\adsi\samples\dsui\scpext\scpcmenu\
- \netds\adsi\samples\dsui\scpext\scpproppage\
- \netds\adsi\samples\dsui\scpext\scpwizard\
- \netds\adsi\samples\dsui\userext\userproppage\
- \netds\adsi\samples\dsui\userext\userwizard\
- \netds\adsi\samples\general\adqi\
- \netds\adsi\samples\general\adserror\
- \netds\adsi\samples\general\adsidump\
- \netds\eap\eaphost
- \netds\fax\devicesetting\
- \netds\fax\faxaccount\
- \netds\fax\faxjoboperations\
- \netds\fax\faxreassign\
- \netds\fax\faxsecurity\
- \netds\fax\foldersenum\
- \netds\fax\outboundrouting\
- \netds\fax\routingextension\
- \netds\fax\sendfax\
- \netds\fax\serverconfig\
- \netds\messagequeuing\c_draw
- \netds\messagequeuing\imp_draw\
- \netds\messagequeuing\mqapitst
- \netds\messagequeuing\mqapitst\
- \netds\messagequeuing\mqf_draw
- \netds\messagequeuing\mqpers\
- \netds\nap\sdkqec
- \netds\nap\shv
- \netds\netmon\experts\blrplate\
- \netds\ras\customdial\
- \netds\ras\phoneentry\
- \netds\rras\eap\
- \netds\rtc\client\cpp\rtcincoming\
- \netds\rtc\client\cpp\rtcoutgoing\
- \netds\rtc\client\cpp\rtcsample\
- \netds\tapi\tapi3\cpp\msp\samplemsp\
- \netds\tapi\tapi3\cpp\pluggable\
- \netds\upnp\dco_dimmerservice\
- \netds\upnp\genericucp\cpp\
- \netds\upnp\registerdevice\
- \netds\wlan\autoconfig
- \security\authorization\azman\azmigrate
- \security\capicom\cpp\isapicertpolicy
- \security\certservices\exit\c++\windows.net\
- \security\certservices\exit\c++\windows2000\
- \security\certservices\policy\c++\windows.net\
- \security\certservices\policy\c++\windows2000\
- \security\credentialprovider
- \tabletPC\advreco\cpp
- \tabletPC\basicinkanalysis\cpp
- \tabletPC\tpcinfo\cpp
- \web\bits\bits_ie\
- \web\bits\upload\
- \web\iis\components\cpp\intermediate
- \web\iis\components\cpp\simple\
- \web\iis\rsca
- \web\networking\asyncdemo\
- \winbase\cluster\win2003\clipbookserver\clipbook serverex\
- \winbase\cluster\win2003\filesharesample\file share sampleex\
- \winbase\rdc
- \winbase\storage\optical\imapi2sample
- \winbase\vss\vshadow
- \winbase\vss\vsssampleprovider
- \winbase\winsat\initiateassessment\cpp
- \winbase\wtsapi\wtsapi\
- \winui\globaldev\cssamp\
- \winui\globaldev\globaldev\
- \winui\muisampleapp
- \winui\pictures\acquisitionplugin
- \winui\pictures\pictureacquisition
- \winui\pictures\pictureacquisitionplugin
- \winui\shell\columnprovider\
- \winui\shell\shelliconoverlay\
- \winui\sideshow\pictures\
- \winui\sideshow\tasks\
- \winui\tsfapp\
- \winui\tsfcompart\
5.5.5
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.
5.5.6
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
5.5.7
The SchemaReader Sample Requires Windows Media Player 11
The Windows Media Player SchemaReader sample requires Windows Media Player 11 to
be installed.
5.5.8
MMC 3.0 Samples Require 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.
5.5.9
TabletPCSetupSample fails to build using MSBuild (msbuild.exe)
MS build does not support setup projects. Visual Studio is required to build TabletPCSetupSample.
5.5.10
The Security Certificate Services Ocspsample Does Not Build On or For Windows
Vista
There is no workaround for this issue.
5.5.11
The Following Windows Media 9 Samples Require Additional Steps to Build
The following samples require additional steps to build:
- \Samples\Multimedia\WindowsMediaServices9\Logging
- \Samples\Multimedia\WindowsMediaServices9\CacheProxy\csharp
To build the Logging and CacheProxy samples:
- Load each of the samples' .sln file into Visual Studio 2005 and allow it to upgrade
the project.
- Add a reference to microsoft.windowsmediaservices.dll by going to Project | Add
Reference... | Browse and then browse to the SDK's include directory and select
microsoft.windowsmediaservices.dll and click OK.
- Build the solution.
5.5.12
The Following TAPI Samples Depend Upon the Directshow Baseclasses
The following TAPI samples depend upon the DirectShow BaseClasses (found in the
SDK Sample directory). If the sample directory is not installed to the default location,
the makefile for the following samples will need to be adjusted to refer to the
new location:
- \netds\tapi\tapi3\cpp\pluggable
- \netds\tapi\tapi3\cpp\tapirecv
- \netds\tapi\tapi3\cpp\tapisend
5.5.13
The 3d9exsample Sample Requires DirectX SDK to Build
The sample multimedia\direct3d\d3d9exsample requires the
DirectX SDK be installed
and the INCLUDE and LIB environment variables updated to build. The DirectX SDK
include directory should be appended to the INCLUDE environment variable, from within
a SDK command prompt. Additionally the DirectX SDK library directory also must be
appended to the LIB environment variable, from within a SDK command prompt. This
will allow the sample to be built using the supplied makefile.
5.5.14
Samples Needing Adminstrative Privilege to Build
The following samples need administrative privilege to build on Windows Vista:
- multimedia\windowsmediaservices9\authentication
- multimedia\windowsmediaservices9\authorization
- multimedia\windowsmediaservices9\eventnotification
- multimedia\windowsmediaservices9\cacheproxy\cplusplus
- multimedia\windowsmediaservices9\datasource
- multimedia\windowsmediaservices9\playlist
- web\iis\components\cpp\intermediate
- winbase\rdc
5.5.15
The Windows Data Access Components documentation describes some samples that are not included in this release of the Windows SDK.
There is no work around for this issue.
5.5.16
Release configuration of the vsssampleprovider cannot be built until the Debug configuration is built.
For the sample located in Samples\winbase\vss\vsssampleprovider
the Release configuration
fails to build the EventLogMsg.h file which is required for compilation to succeed. On the other
hand this file is built by the Debug configuration.
To work around this issue, first build the debug configuration before attempting to
build the release configuration. This creates the EventLogsMsg.h file which can be subsequently
be used by the release configuration
5.5.17
The Win32HostingWPFPage sample located in Samples\WPFSamples\MigrationInterop\Win32HostingWPFPage fails to build
The Win32HostingWPFPage sample fails to build using MSBuild in the SDK build environment.
There is no workaround for this issue.
5.5.18
The Quickstart4 sample located in Samples\wpfsamples\Intro\QuickStart4\CSharp\
fails to build
The Quickstart4 sample fails to build using MSBuild in the SDK build environment.
There is no workaround for this issue.
5.5.19
The sample \wpfsamples\GlobalizationLocalization\GlobalizationHomepage\MicrosoftSaudiArabiaHomepage.csproj
fails to build
The sample in Samples\wpfsamples\GlobalizationLocalization\GlobalizationHomepage\
can be ignored. The
working version of the sample can be found in the
Samples\wpfsamples\GlobalizationLocalization\GlobalizationHomepage\XAML\
folder.
5.5.20
Capicom samples fail to build
The following samples fail to build:
- Samples\Security\capicom\c_sharp\chainsh
- Samples\Security\capicom\c_sharp\storesh
- Samples\Security\capicom\c_sharp\xmldsig
- Samples\Security\capicom\vbs\Cversion.vbs
These samples require capicom.dll (located in the Bin directory) to be registered. This can be done implicitly by
running SignTool (signtool.exe, located in the Bin directory) or explicitly using regsvr32.exe.
5.5.21
Some x509 Samples can not be found
Some x509 sample are installed under Security\X509 Certificate Enrollment
.
5.5.22
Windows Media Player online store plug-in wizard can't be found
Windows Media Player online store plug-in wizard must be installed manually.
The Visual Studio Registration utility does not install the Windows Media Player
online store plug-in wizard as stated in the Windows Media Player SDK documentation.
For instructions on installing the plug-in wizard manually, see Readme for Windows
Media Player 11 SDK in the MSDN Library.
5.5.23
Tablet PC RecoDLL sample will not self register
The Tablet PC RecoDLL sample contains an outdated resource file, recodll.rc
.
Consequently, although the sample DLL builds, it cannot self register.
A fix is planned for a later release.
To use the sample properly, download the
Updated recodll.c Source File for Tablet PC RecoDLL Sample from the MSDN Download and Code Center.
Save the file to your computer, and then double click the application to start the installation.
Save recodll.rc and RecoDll.vcproj to the Tablet PC RecoDLL sample source folder, overwriting the originals.
The default destination is %destination drive%:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\TabletPC\RecoDLL\CPP.
5.5.24 Samples\SysMgmt\WMI\VC\Decoupled
will not build using Visual Studio
To build
Samples\SysMgmt\WMI\VC\Decoupled
using Visual Studio:
- Delete the contents of
Samples\SysMgmt\WMI\VC\Decoupled
- Move the folders:
Samples\SysMgmt\WMI\VC\Event_Consumer
Samples\SysMgmt\WMI\VC\Event_Provider
Samples\SysMgmt\WMI\VC\Instance_Provider
to Samples\SysMgmt\WMI\VC\Decoupled
. - Build and Run each of these samples under
Samples\SysMgmt\WMI\VC\Decoupled
individually as per directives given in the help docs.
5.5.25 NAP sample code does not run under Vista
The NAP Sample code needs changes to work with Vista RTM. It will build, but will not work
until the following changes are made:
Change 1:
File: \NetDS\NAP\SHA\EXE\Callback.cpp
Line: 368
Current:
value.vendorSpecificVal.vendorId = MicrosoftVendorId;
Should be:
value.vendorSpecificVal.vendorId = QuarSampleSystemHealthId;
Change 2:
File: \NetDS\NAP\SHV\SampleShv.cpp
Line: 348
Current:
goto Cleanup;
Should be:
[removed]
Change 3:
File: \NetDS\NAP\SHV\SampleShv.cpp
Line: 514
Current:
(pAttrValue->vendorSpecificVal.vendorId == MicrosoftVendorId) &&
Should be:
(pAttrValue->vendorSpecificVal.vendorId == QuarSampleSystemHealthId) &&
Change 4:
File: \NetDS\NAP\SHV\SampleShv.cpp
Line: 524
Current:
(pAttrValue->vendorSpecificVal.vendorId == MicrosoftVendorId) &&
Should be:
(pAttrValue->vendorSpecificVal.vendorId == QuarSampleSystemHealthId) &&
5.5.26 Schema files relating to Windows PowerShell samples are missing
The schema files for the PowerShell samples are located in SysMgmt\WindowsPowerShell\Schemas
.
5.5.27
WCF Samples Setup Batch File May Not Work with IIS7
The WCF samples setup script, Setupvroot.bat, works on Windows Vista only if you
have Internet Information Services (IIS) 6.0 compatibility installed. To do this,
either use the manual setup instructions provided in the SDK or set up IIS 6.0 compatibility
by doing the following:
- Click the Start button and select Control Panel.
- Select Programs in the Control Panel dialog.
- Select Turn Windows Features on or off.
- The User Account Control dialog is displayed. Click Continue.
- The Windows Features dialog is displayed. Expand the item labeled Internet Information
Services.
- Expand the item labeled World Wide Web Services.
- Expand the item labeled Application Development Features.
- Make sure the following items are selected:
- .Net Extensibility
- ASP.NET
- ISAPI Extensions
- ISAPI Filters
- Expand the item labeled Web Management Tools and make sure IIS Management Console
is selected.
- Expand the item labeled IIS 6 Management Compatibility and make sure IIS 6 Scripting
Tools is selected (other options auto-select when you do this).
- Click OK.
5.5.34
WCF Samples Setup Batch File May Not Work with IIS7
The WCF samples setup script, Setupvroot.bat, works on Windows Vista only if you
have Internet Information Services (IIS) 6.0 compatibility installed. To do this,
either use the manual setup instructions provided in the SDK or set up IIS 6.0 compatibility
by doing the following:
- Click the Start button and select Control Panel.
- Select Programs in the Control Panel dialog.
- Select Turn Windows Features on or off.
- The User Account Control dialog is displayed. Click Continue.
- The Windows Features dialog is displayed. Expand the item labeled Internet Information
Services.
- Expand the item labeled World Wide Web Services.
- Expand the item labeled Application Development Features.
- Make sure the following items are selected:
- .Net Extensibility
- ASP.NET
- ISAPI Extensions
- ISAPI Filters
- Expand the item labeled Web Management Tools and make sure IIS Management Console
is selected.
- Expand the item labeled IIS 6 Management Compatibility and make sure IIS 6 Scripting
Tools is selected (other options auto-select when you do this).
- Click OK.
6. Windows SDK Product Support
The Windows SDK is provided "as-is" and is not supported by Microsoft.
For technical support, there are a number of options:
6.1 Professional Support for Developers
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.
6.2 MSDN Online
MSDN online support allows access to
Developer Support search, support incident submission, technical and product information,
support highlights, service packs, downloads, webcasts, and MSDN Online's member communities.
7. Feedback
Your feedback is important to us. Your participation and feedback through the
Windows Vista Newsgroups
is appreciated.
Copyright © 2006 Microsoft Corporation. All rights reserved. Legal Notices: http://www.microsoft.com/legal/.