This version of the Microsoft Windows SDK is intended to support only the Microsoft® Pre-Release Software WinFX® Runtime Components - November Community Technology Preview (CTP) on Microsoft® Windows® XP and Microsoft® Windows Server® 2003 only.

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), or Microsoft Windows Server 2003 Service Pack 1 (SP1) versions of Windows.

Important This version of the Windows SDK is available only as a DVD ISO image that must be burned to a DVD and installed from that media. The image 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.

Important This version of the Windows SDK targets specific versions of Windows and has other restrictions. This version:

• Is intended to support only Microsoft Pre-Release Software WinFX Runtime Components - November Community Technology Preview (CTP). While the SDK includes additional Win32 content, it supports only WinFX content and development with WinFX at this time. In an upcoming pre-release, we expect the SDK to deliver full support for both Win32 and WinFX development on Windows Vista, Windows XP SP2, and Windows Server 2003 SP1 operating systems.
   
• Is supported for use only on Windows XP SP2 and Windows Server 2003 SP1. It is not supported on any publicly available build of Windows Vista.

Note To use features for WinFX, the managed programming model for Windows, install the version of the WinFX Runtime Components compatible with this CTP release.

Important In this version of the SDK, the customized setup options are not implemented completely. In future releases, the Windows SDK Setup Wizard will provide options for installing all features for complete Windows development support as well as customized options specifically for WinFX and Win32 content.

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.

• It is strongly recommended that you install this pre-release version of the Windows SDK in a test environment, not a production environment. There are several known issues with this release. Because this is a pre-release edition, many of the known issues are identified in this document. Please read the installation instructions and known issues before installing.
   
• To learn more about Known Issues and to find additional information about Windows Vista, see The MSDN Online Windows Vista Developer Center. The Developer Center is focused on keeping developers up-to-date on how they can take advantage of Windows Vista's rich new client features in their applications. Visit the Developer Center often to see new articles, read monthly columns, participate in the Windows Vista Beta Newsgroups, download sample code, and read the Editor's Web Log.

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.

Supported Compiler

Supported Platforms

This release of the Windows SDK is a community technology preview and is a snapshot of the daily builds of the SDK. The documentation, samples, and tools provided in this release are preliminary and subject to change.

• This pre-release of the Windows SDK supports x86 platforms for building and running samples.
• Support for the x64 platform is not completely functional, but should work for most core scenarios.
• The IA64 platform is not supported in this release.  

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. 

Installation Instructions

1. If you intend to install WinFX components available in the Windows SDK, install the Microsoft WinFX Runtime Components 3.0.
2. Download the Windows SDK to your desktop, and then burn the image to a DVD or use
3. Insert the SDK DVD into a DVD-ROM drive and click setup.exe to begin the installation.
4. Follow the instructions in the Windows SDK Setup wizard.
   • Note: if you choose Custom Install, a setenv error will occur. You can ignore this error and the components you selected will be installed as expected.
5. Optional Install Microsoft^® Visual Studio^® 2005 (RTM version)
6. Optional  Install the Visual Studio 2005 Extensions for WinFX.

Note This version of the Windows SDK is not supported on any currently publicly available builds of Windows Vista.

Note If you intend to use Visual Studio to develop WinFX applications, you must install the Windows SDK before installing the Visual Studio 2005 Extensions for WinFX. It is essential that you use the RTM version of Visual Studio with this release..

Access the Windows SDK through the Start menu at Microsoft Windows SDK. This Start menu folder contains pointers to the documentation (which contains the samples for WinFX), tools, and debug and release build environments.

Known Issues

This release of the Windows SDK is a community technology preview and is a snapshot of the daily builds of the SDK. The documentation, samples, and tools provided in this release are preliminary and subject to change. It is recommended that you use this preliminary release of the Windows SDK in a test environment.

This release has the following known issues. Known issues are categorized by content type.

General Development

The following entry describes a known general development issue in the Windows SDK.

The Windows SDK download is an image of the SDK that is not installable via download and execution. It must be burned to a DVD and installed from that media.

 

Accessing the ISO File - An ISO image file is an exact representation of a CD, including the content and the logical format. The most common use of an image file is to write it to a blank CD-R resulting in an identical copy of the original CD including file name and volume label information. ISO Images can also be extracted directly to a file location by many CD-R utilities, including the tool below. For more information about image files, please visit the MSDN FAQ.

Mounting ISO files virtually - You can use the Virtual CD-ROM Control Panel for Windows XP tool to mount the ISO image file virtually as CD-ROM devices without burning the image to a DVD. This tool is provided here for your convenience, and is unsupported by Microsoft Product Support Services.

Tools

• For x64 and x86, if the path contains any instances of a parenthesis, setenv.cmd doesn’t run properly

  The workaround is to copy the path to Notepad and manually put quotation marks around any portions of the path that contains the parenthesis.  Then paste the newly made path into the command window as 'set path=%your constructed path%'

  For example:

  Path=C:\program files\microsoft sdks;C:\program files\directx sdk (October)

  Change to:

  Set Path= C:\program files\microsoft sdks;"C:\program files\directx sdk (October)"

• Known issues and limitations with WCF tools

• Known issues with the Microsoft Command Shell (MSH)

This section includes information about installing the Windows "Monad" Shell and what's changed since other recent previews.

Installing the Windows "Monad" Shell Beta 2 (for .NET Framework 2.0 RC and RTM versions)

IMPORTANT If you need to uninstall the .NET Framework to upgrade it to the RC or RTM version, and you have an earlier build of the Windows "Monad" Shell installed, then you must uninstall Monad (from Add/Remove Programs) BEFORE you uninstall the earlier .NET Framework release. Otherwise, Monad uninstall will fail because it cannot detect the correct .NET Framework version.

1. To install or un-install Monad you must have admin privileges.
2. If you have Beta 1 of Monad:
   1. Back up any custom profiles you have created if you want to reuse them.
   2. In Control Panel, go to Add/Remove Programs and remove any entry containing "Microsoft Command Shell."
3. If you have an installation that pre-dates Beta 1:
   1. In Control Panel, go to Add/Remove Programs and remove any entry containing "Windows Command Shell Preview."
   2. You may need to manually remove the directory “C:\Program Files\Microsoft Command Shell Preview” and/or “C:\Program Files\Windows Longhorn Command Shell Preview."
4. Ensure you are running on Windows XP SP2 or Windows Server 2003 SP1.
5. Verify that you have the correct version of the .NET Framework, RC/RTM.050727-xxxx. To check whether you have the correct version perform the following:
   1. In your %windows%\Microsoft.NET\Framework directory, check to see if you have a v2.0.50727 sub-directory. If you do not have this directory you do not have an RC/RTM release of the .NET Framework.
   2. If you have this sub-directory, right click on a DLL in this directory and choose Properties. Click on the Version tab, then click File Version under Item Name. The value should be 2.0.50727.42 (RTM.050727-4200). However this Monad release should work with earlier versions of 50727 such as 50727.26.
   3. If you do not have the right version of the .NET Framework then you need to install it from http://lab.msdn.microsoft.com/vs2005/get.
6. Run the MSI package in the x86 directory (for 32-bit machines) or the x64 directory (for 64-bit machines).

Changes to Windows "Monad" Shell since Beta 2 (for .NET Framework 2.0 Beta 2)

Although this release is essentially the same code base as the previous Beta 2 release (except moved to the RC/RTM version of .NET Framework 2.0), a few changes were made:

• Monad's ExecutionPolicy is now configured to "Restricted" by default. This is a new value for ExecutionPolicy. In Restricted mode, scripts (.msh files) cannot be run and .mshxml files (types.mshxml and *.format.mshxml files) can only be run if they are signed by a trusted publisher (.mshxml files are treated the same as they are by the "AllSigned" policy). For msh.exe, this value is controlled via the registry setting "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSH\Microsoft.Management.Automation.msh\ExecutionPolicy". The earlier Beta 2 release defaulted to an ExecutionPolicy of "RemoteSigned".

• For other shells, the ExecutionPolicy is controlled via the registry setting "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSH\<ShellId>\ExecutionPolicy" where "<ShellId>" can be obtained from the $shellid variable inside the shell.

• When Monad first starts up it may ask a question "Do you want to run software from this untrusted publisher?" for the file "types.mshxml", published by Microsoft. You can choose to not load the file, but the file (and the *.format.mshxml files, which Monad will also prompt for if you do not select [A] for "Always run" for types.mshxml) controls the display and formatting of Monad and the experience in Monad will be degraded if it is not loaded. To avoid this prompt in the future, either select [A] for "Always run", or change the ExecutionPolicy from "Restricted" to "RemoteSigned".

• The error text for certain execution errors references the "about_signing" help file. This file is not installed by Monad setup. However it is included here as a separate file. To enable this help, copy the file about_signing.help.txt to your Monad installation directory. You may need to exit and restart Monad for it to pick up the new file. The file is a plain text file which can be viewed in any text editor or word processor.

• If you see an error at startup "The file "C:\Documents and Settings\All users\Documents\msh\profile.msh cannot be loaded. The execution of scripts is disabled on this machine" then either change the ExecutionPolicy from "Restricted" to "RemoteSigned", or sign the files using the set-authenticodesignature cmdlet (the error message is misleading; execution of .mshxml files is not entirely disabled when ExecutionPolicy is "Restricted", but they must be signed by a trusted publisher). The "about_signing" help file has more details. You can also delete the file; in the initial configuration, the profile.msh file does not add any functionality to Monad.

• If do load the profile.msh file, and you have previously installed an earlier version of Monad, then on startup you may see a series of errors like:
  set-alias : The AllScope option cannot be removed from the alias 'cat'.

At C:\Documents and Settings\All Users\Documents\msh\profile.msh:9 char:10
+ set-alias <<<< cat get-content
 

To fix this, either delete the file named ("C:\Documents and Settings\All Users\Documents\msh\profile.msh" in this example), or remove all the "set-alias" lines from it. Aliases defined in profile.msh in earlier versions of Monad are now defined internally by Monad before the profile is run, therefore the definitions in profile.msh generate an error attempting to redefine the alias.

• Cmdlet parameters that are literal numbers will now get treated as numbers, whereas previously they used to be treated as strings. This may affect a script if the type of the parameter can be converted from a string but not from an integer. The user fix is to enclose the literal number in quotes. This change was in the earlier Monad Beta 2 but was not well communicated before.

• Tb3x.exe has been deprecated and removed from the SDK

Tb3x.exe has been deprecated and removed from the SDK.   There is no known workaround for this issue.

Headers and Libraries

• The Application Verifier tool is not available in the Windows SDK

• Some include files do not appear to be available

• Linker tools sometimes throw errors at link time

• To support Winsock 2.0 development, a header file needs to be commented out

Compilers

• The J# Compiler Is Not Available in this Version of the Windows SDK

• Debugging Windows Presentation Foundation (WPF) applications with Kernel Debugger Active may result in an error

Samples

• Samples that reference WindowsFormsIntegration.dll may require modifications to the project file to compile

• The following WinFX 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 workaround for this issue.
 

Cross-Technology Samples	Windows Presentation Foundation	Windows Communication Foundation	Windows Workflow Foundation
AlarmClock	Avalon Calculator (C#)	DataBindingCS	AspRoles
GadgetUILibrary	Controls_ContentModel (C#)	DeadLetter
MoodOrb	DataGrid (C#)	ETWTracing
MSBuildG	GraphCalc (C#)	Federation Sample
RecipeViewer	HostingAxInWpfWithXaml (C#)	Http
	Label_snip (C#)	IETWTracing
	MediaElement (C#)	IndiCalc
	mousewheelButton (VB)	IndigoToMSMQ
	Surfin (C#)	InfoCard
	UIATextPattern_snip (C# & VB)	Instance Lifetime
	Win32HostingWPFPageCPP (C++)	MessageInterceptor
		MsmqActivation
		Poison
		RouteByBody
		Transacted
		Two-way

• .NET Framework samples are available only via allsamples.zip

   

  The .NET Framework samples are available in the Windows SDK, but only via allsamples.zip. These samples are not available via the samples documentation.  To work around this issue, extract the .NET Framework samples from the allsamples.zip file, which is available in the ...\Microsoft SDKs\Windows\v1.0\Samples directory.

   

• The following non-WinFX samples do not compile in this version of the Windows SDK

Win32 development is not supported in this version of the Windows SDK. As a result, the samples listed below do not compile. Additionally, none of the DirectShow samples compile.  There is no workaround for this issue.

\com\administration\explore.vc	\netds\activedirectory\propsheethost	\sysmgmt\mmc\cmenu
\com\administration\spy\comspy	\netds\adsi\samples\activedir\adevent	\sysmgmt\mmc\complete
\com\administration\spy\comspyaudit	\netds\adsi\samples\activedir\sid\vc	\sysmgmt\mmc\cutcopy
\com\administration\spy\comspyctl	\netds\adsi\samples\activedir\user\vc	\sysmgmt\mmc\extens
\com\fundamentals\common	\netds\adsi\samples\activedir\wkguid\vc	\sysmgmt\mmc\menubtn
\dataaccess\oledb\rowsetviewer	\netds\adsi\samples\dsui\scpext\scpcmenu	\sysmgmt\mmc\multisel
\dataaccess\oledb\sampprov	\netds\adsi\samples\dsui\scpext\scpproppage	\sysmgmt\mmc\nameext
\dataaccess\osp\vc	\netds\adsi\samples\dsui\scpext\scpwizard	\sysmgmt\mmc\nodes
\multimedia\audio\multichan	\netds\adsi\samples\dsui\userext\userproppage	\sysmgmt\mmc\openserv
	\netds\adsi\samples\dsui\userext\userwizard	\sysmgmt\mmc\proppage
	\netds\adsi\samples\general\adqi	\sysmgmt\mmc\taskpads
	\netds\adsi\samples\general\adsidump	\sysmgmt\wmi\vc\simpleclient
	\netds\bluetooth	\tabletpc\advreco
	\netds\fax\printsdi	\web\bits\bits_ie
	\netds\gqos\qoslist	\web\bits\upload
	\netds\messagequeuing\c_draw	\web\iis\components\cpp\intermediate
	\netds\messagequeuing\imp_draw	\web\iis\extensions\formdump
	\netds\messagequeuing\mqapitst	\web\netmeeting\nmui
	\netds\messagequeuing\mqf_draw	\web\xml\mfc_tree
	\netds\netshell	\winbase\cluster\win2003\clipbookserver\clipbook serverex
	\netds\peertopeer\contacts	\winbase\cluster\win2003\filesharesample\file share sampleex
	\netds\peertopeer\invitations	\winbase\winnt\perfcounter
	\netds\peertopeer\people near me	\winbase\wtsapi\wtsapi
	\netds\rpc\filerep\filerepasyncpipe	\winui\globaldev\cssamp
	\netds\rtc\client\cpp\rtcincoming	\winui\sendto
	\netds\rtc\client\cpp\rtcoutgoing	\winui\shell\bandobjs
	\netds\syncmgr\syncdir	\winui\shell\columnprovider
	\netds\tapi\tapi3\cpp\fileterm	\winui\shell\dragimg
	\netds\tapi\tapi3\cpp\incoming	\winui\shell\dropext
	\netds\tapi\tapi3\cpp\msp\mspbase	\winui\shell\enumdesk
	\netds\tapi\tapi3\cpp\msp\samplemsp	\winui\shell\sampview
	\netds\tapi\tapi3\cpp\outgoing	\winui\shell\shellext
	\netds\tapi\tapi3\cpp\pluggable	\winui\shell\shelliconoverlay
	\netds\tapi\tapi3\cpp\tapirecv
	\netds\tapi\tapi3\cpp\tapisend
	\netds\upnp\genericucp\cpp

• The Web\Behaviours\Library\ToolTips sample does not currently run

The Web\Behaviours\Library\ToolTips sample does not currently run. There is no known workaround for this issue.

• Some samples do not compile because compile-time warnings are treated as errors

These samples do not currently compile with the version of the compiler shipped with this SDK because compile-time warnings are treated as errors:

• netds\winsock\appletalk
• netds\winsock\overlap
• netds\winsock\simple
• winbase\indexing\smpfilt
• winbase\io\enummount
• winbase\io\floppy
• winbase\WtsApi\TSSysInf\Client
• winui\cursor
• WinUI\Input\Ime\FullIME
• winui\input\Ime\multiui
• winui\input\mouseinfo
• WinUI\Input\Ime\FullIME

To work around this issue, remove the compile-time switch /WX in each sample's makefile. However, as a rule you should NOT base your development using any code that produces warnings.

• Two samples ship invalid project files (.vcproj)

The following samples ship invalid project files (.vcproj). These files are used to build the sample on the command line using vcbuild.exe, which is included in the SDK.

• Samples\SysMgmt\QueryLog
• Samples\SysMgmt\Subscriber

Please use the supplied makefiles to build the samples.

• Some NetDS samples require Visual Studio 2003 to build

All samples installed in the \Microsoft%20%SDKs\Platform\Samples\NetDs\NAP directory require that Microsoft Visual Studio 2003 be installed to build. These samples do not compile from the command line. There is no known workaround for this issue.

• Active Template Library (ATL) and Microsoft Foundation Class (MFC) samples require Visual Studio to build

Some samples in the Windows SDK use Active Template Libarary (ATL) and/or Microsoft Foundation Class (MFC) technologies found in Visual Studio. Samples using these technologies require Visual Studio to build. For example, samples that include the afxwin.h or atlbase.h require MFC and ATL respectively and require Visual Studio to build.  There is no known workaround for this issue.
 

• Reference pages for the Windows Presentation Foundation Attached Properties are missing

• Copy Code sometimes produces an error

• Some topics in the documentation display an Internet Explorer Script Error

• Documentation filters do not work properly

• Hyperlinks are broken in Tools Reference document available from the Start menu