Microsoft^® Windows^® SDK Readme for the January 2006 CTP

Welcome to the Microsoft^® Windows^® Software Development Kit (SDK) for the January 2006 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), 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 supported on Windows Vista build 5270, which is available from the MSDN Universal Subscribers site on MSDN and from the Beta customer locations.
• Supports Microsoft Pre-Release Software WinFX Runtime Components - January Community Technology Preview (CTP) for Windows XP SP2 and Windows Server 2003 SP1, which is available publicly from the Download Center.

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

Note In this version of the SDK, the customized setup options are not implemented completely. Custom options on the Installation Options screen are viewable, but cannot be selected. In future releases, the Windows SDK Setup Wizard will provide fully functional 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.

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.

3. Supported Platforms

• This pre-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. 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

5. Installation Instructions

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:

1. If you intend to use the WinFX content available in the Windows SDK, install the Microsoft WinFX Runtime Components 3.0 for the January CTP from the Download Center.
2. Download the Windows SDK from Download Center, burn the image to a DVD, and install the SDK on your local hard disk.  (Note: the Windows SDK details page in the Download Center has additional information about tools you can use to create the setup image without burning the image to a DVD.)
3. Insert the SDK DVD into a DVD-ROM drive and click setup.exe to begin the installation. Follow the instructions in the Windows SDK Setup wizard.
4. Optional  Install Microsoft^® Visual Studio^® 2005 (this Windows SDK is compatible with the RTM version of Visual Studio).
5. Optional  Install the Visual Studio 2005 Extensions for WinFX for January CTP from the Download Center.

To install on Windows Vista:

1. If you intend to use the WinFX content available in the Windows SDK, install the Microsoft WinFX Runtime Components using the following methods:
   1. On a machine with Windows Vista December CTP installed, uninstall the December CTP WinFX Runtime components.
   2. Install the Microsoft WinFX Runtime Components 3.0 for the January CTP from the Download Center.
2. Download the Windows SDK from Download Center, burn the image to a DVD, and install the SDK on your local hard disk.  (Note: the details page for the Windows SDK in the Download Center has additional information about tools you can use to create the setup image without burning the image to a DVD.)
3. Insert the SDK DVD into a DVD-ROM drive and click setup.exe to begin the installation. Follow the instructions in the Windows SDK Setup wizard.
4. Optional  Install Microsoft^® Visual Studio^® 2005 (this Windows SDK is compatible with the RTM version of Visual Studio).
5. Optional  Install the Visual Studio 2005 Extensions for WinFX for January CTP from the Download Center.

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 version of Visual Studio identified in the Installation instructions in WinFX Runtime Components setup instructions.

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.

Note  Documentation for the Windows SDK, is also available on MSDN Online at:  http://windowssdk.msdn.microsoft.com/library. This content is updated with every Windows Vista CTP release.

6.1.1    Custom Installation Options do not work in this release

In the Windows SDK setup, the custom installation options on the Installation Options screen are viewable, but cannot be selected. Custom installation is not available.  To work around the issue and complete the install, go back and select a Typical install. Custom installation will work in an upcoming release of the Windows SDK.

6.1.2    The Windows SDK does not support UDDI development using .NET

The Windows SDK does not support UDDI development using .NET. As a result, three UDDI samples that require .NET will not compile in this version of the SDK. There is no known workaround for this issue.

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.

6.4.3    UISpy.exe fails to run with 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    Known issues with Windows Communication Foundation tools

There are known issues with two Windows Communication Foundation tools: SvcConfigEditor.exe and SvcTraceViewer.exe

SvcConfigEditor.exe

·         Federation parameters cannot be edited for the Security section in the custom binding editor.

·         The XPath filter dialog does not support namespaces.

·         It is not possible to edit endpoint/instance headers.

·         Not all comments are preserved after saving the configuration.

SvcTraceViewer.exe

• SvcTraceViewer.exe does not remove generated temp files from the %temp% folder.

• ETL traces must be re-saved before they can be viewed; therefore, the "Save As" dialog will appear after you open a trace.

 

Workaround

There are no known workarounds for these issues.

6.4.5 SvcConfigEditor.exe Does Not Activate Cross-process Activity Tracking When Activity Tracking Is Activated for a Source

Local traces will not be correlated to traces on another process or system, and multiple nodes (client/server) do not display in the TraceViewer’s Activity view.

Workaround

Manually activate this feature. In the SvcTraceViewer’s config file, add “propagateActivity=true” to the source of your choice using a text editor:

<sources>
<source name="System.ServiceModel" switchValue="Verbose, ActivityTracing" propagateActivity="true" >
<listeners>
<add name="xml" />
</listeners>
</source>
<source name="System.ServiceModel.MessageLogging" switchValue="Verbose">
<listeners>
<add name="xml" />
</listeners>
</source>
</sources>

6.4.6 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 wsdl:binding”

Svcutil.exe also fails to generate a configuration file in this case.

There is no workaround at this time. This issue will be addressed in a future release.

6.4.7    Known issues with the Microsoft Command Shell (Monad)

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).

• Windows SDK setenv.msh ("Monad") does not preserve path information

The Windows SDK's implementation of setenv.msh ("Monad") does not preserve path information when called with an invalid parameter.  To work around this issue, close the command window and restart it.

6.4.8    Known issues with Windows Workflow Foundation (WWF)

There are several known issues with Windows Workflow Foundation (WWF) in this SDK release. See the online Windows Workflow Foundation ReadMe for a complete list.

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

These samples reference the WindowsFormsIntegration DLL in their project files and call its APIs. The WindowsFormsIntegration DLL is not installed through the same process or in the same location as the primary WinFX DLLs, and it is not added to the Global Assembly Cache as part of any installation. This issue affects the following samples:

• Hosting a Windows Forms Control in an "Avalon" Page
• Host a Simple "Avalon" Control in a Windows Form

The project files must include a hint path to find the WindowsFormsIntegation DLL in order to compile these samples. The hint path should be correct in most cases. However, if you have changed installation options, it may be necessary to modify the hint path in order to properly reference the DLL and successfully compile the samples. By default, the location of this DLL is Program Files\Reference Assemblies\Microsoft\Avalon\VersionNumber. Find the location of the WindowsFormsIntegration DLL on your system if that location is different and modify the project file(s) as necessary.

In addition, the "Hosting a Windows Forms Control in an "Avalon" Page" sample may require the following code modifications to run as expected:

AvalonHost project, Page1.xaml file line 100: replace Height="Auto" with Height="300"
AvalonHost project, Page1.xaml.cs file line 34: replace wfh.FindName("mc") with wfh.Children[0]

To work around this issue, replace the English term, "NTAUTHORITY\NETWORK SERVICE" in the setup.bat file with the appropriate term in the local language.

6.6.2    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 known workaround for this issue.

.NET Framework	Windows Presentation Foundation	Windows Communication Foundation	Cross-Technology
ASP Roles (C# only) Background Update (C# only) BEREncoding (C++ only) Bind Validation (C# only) Control Template Examples (VB only) Dsml Batch Request (C++ only) Dsml Exceptions (C++ only) Dsml Paged Search (C++ only) Dsml Read Root DSE (C++ only) Dsml Send Request (C++ only) LDAP Async Send (C++ only) LDAP Exceptions (C++ only) LDAP Paged Search (C++ only) LDAP Print Domain (C++ only) LDAP Read Root DSE (C++ only) LDAP Referral (C++ only) LDAP Send Request (C++ only) Mailer (C++ only) On Demand (C++ only)	Avalon Hosting Windows Forms Control (C# only, Windows Vista x64 only) Control Template Examples (VB only) HostingAxInWpfWithXaml (C# only) HostingWfInWpf (C# only, Windows Vista x64 only) HostingWfInWpfWithXaml (C# only, Windows Vista x64 only) HostingWpfUserControlinWf (C# only, Windows Vista x64 only) Tab Control Styles (VB only, Windows Vista x64 only) Windows Forms Hosting Avalon Control (C# only, Windows Vista x64, Windows XP x86, Windows XP x64) WPFwithWFandDataBinding (C# only, Windows Vista x64 only)	Droppable Message Interceptor (C# only, Windows Vista x64 and x86, Windows XP x64) ETWTracing (VB only) Http (Windows XP x64 only) Load Balancer (C# and VB) Message Interceptor (C# only, Windows Vista x64 and x86, Windows XP x64) Operation Requirement (compiles, doesn't run cross-machine) Transaction Behavior (compiles, doesn't run cross-machine) User Name Over Certificate (C# only, Windows Vista x64 and x86, Windows XP x64) XML Formatter (compiles, doesn't run cross-machine)	Alarm Clock Gadget UI Library Mood Orb MSBuildG Recipe Viewer

 

6.6.3    The following non-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. Additionally, none of the DirectShow samples compile. There is no workaround for this issue.

\com\administration\spy\comspy \com\administration\spy\comspyaudit \com\administration\spy\comspyctl \com\fundamentals\common \com\services\crm\crmfilestest\filetest.net\my project \com\services\crm\crmmonitor\vbmonitor.net\my project \com\services\transaction\samplebank\common \com\services\transaction\samplebank\csharpacct \com\services\transaction\samplebank\vbacct\my project \dataaccess\oledb\rowsetviewer \dataaccess\osp\vc \multimedia\audio\multichan \multimedia\directshow\capture\amcap \multimedia\directshow\filters\pushsource \multimedia\directshow\players\texture3d9 \multimedia\directshow\vmr9\multivmr9\gameplayer \multimedia\directshow\vmr9\vmr9allocator \multimedia\directshow\vmr9\watermark \multimedia\directshow\vmr9\windowless \multimedia\gameux\gameexplorerapisample\cpp \multimedia\gameux\gameexplorerapisample\gdf \multimedia\windowsmediaservices9\authentication \multimedia\windowsmediaservices9\authorization \multimedia\windowsmediaservices9\cacheproxy\cplusplus \multimedia\windowsmediaservices9\cacheproxy\csharp \multimedia\windowsmediaservices9\datasource \multimedia\windowsmediaservices9\eventnotification\contextsampleasppage \multimedia\windowsmediaservices9\logging \multimedia\windowsmediaservices9\playlist \multimedia\wmp_11\cpp\remoteskin \multimedia\wmp_11\cpp\wmphost \multimedia\wmp_11\cpp\wmpml \multimedia\wpd\wpdapisample \netds\adsi\samples\activedir\sid\vc \netds\adsi\samples\activedir\user\vc \netds\adsi\samples\activedir\wkguid\vc \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\adsidump \netds\bluetooth \netds\gqos\qoslist \netds\http\server \netds\http\serviceconfig \netds\messagequeuing\csharp_draw \netds\nap\sdkqec \netds\nap\sha\dll \netds\nap\sha\exe \netds\nap\shv \netds\netmon\experts\blrplate \netds\netshell \netds\peertopeer\group chat \netds\peertopeer\pnrp \netds\rpc\filerep\filerepasyncpipe \netds\rras\rqs\server \netds\syncmgr\syncdir \netds\tapi\tapi3\cpp\fileterm \netds\tapi\tapi3\cpp\incoming \netds\tapi\tapi3\cpp\msp\mspbase \netds\tapi\tapi3\cpp\msp\samplemsp \netds\tapi\tapi3\cpp\outgoing \netds\tapi\tapi3\cpp\pluggable \netds\tapi\tapi3\cpp\tapirecv \netds\tapi\tapi3\cpp\tapisend \netds\winsock\appletalk \netds\winsock\simple \security\capicom\c_sharp\chainsh \security\capicom\c_sharp\storesh \security\capicom\cpp\isapicertpolicy \security\certservices\encode \sysmgmt\mmc\cmenu \sysmgmt\mmc\complete \sysmgmt\mmc2.1\threadingsample

\sysmgmt\mmc\extens \sysmgmt\mmc\menubtn \sysmgmt\mmc\multisel \sysmgmt\mmc\nameext \sysmgmt\mmc\nodes \sysmgmt\mmc\openserv \sysmgmt\mmc\proppage \sysmgmt\mmc\taskpads \sysmgmt\mmc\wmi \sysmgmt\mmc2.1\actionssample \sysmgmt\mmc2.1\dragdropsample \sysmgmt\mmc2.1\extendingcomputermanagementsample \sysmgmt\mmc2.1\extensiblesnapinsample \sysmgmt\mmc2.1\extensiontopropertysheetsample \sysmgmt\mmc2.1\extensiontosnapinsample \sysmgmt\mmc2.1\helpsample\helpsamplereference \sysmgmt\mmc2.1\htmlviewsample  \sysmgmt\mmc2.1\initializationwizardsample \sysmgmt\mmc2.1\localizedregistrationsample\resource-en \sysmgmt\mmc2.1\messageviewsample \sysmgmt\mmc2.1\modaldialogsample \sysmgmt\mmc2.1\onscopechangesample \sysmgmt\mmc2.1\persistencesample \sysmgmt\mmc2.1\propertysheetsample \sysmgmt\mmc2.1\selectionformviewsample \sysmgmt\mmc2.1\selectionlistviewsample  \sysmgmt\mmc2.1\servicesmanagersample\resourcedll \sysmgmt\mmc2.1\simplesnapinsample \sysmgmt\mmc2.1\standardverbssample \sysmgmt\mmc2.1\statussample \sysmgmt\mmc2.1\viewswitchingsample \tabletpc\advreco \tabletpc\autoclaims\c# \tabletpc\autoclaims\vb.net \tabletpc\autoclaims15\c# \tabletpc\basicinkanalysis\basicinkanalysissample\properties \tabletpc\inkclipboard \tabletpc\inkcollection\c# \tabletpc\inkcollection\vb.net \tabletpc\inkdivider\c# \tabletpc\inkerase\c# \tabletpc\inkhittest \tabletpc\inkrecognition\c# \tabletpc\inkrecognition\vb.net \tabletpc\inkzoom \tabletpc\scannedpaperform \tabletpc\serialization \web\bits\bits_ie \web\iis\components\cpp\intermediate \web\iis\components\cpp\mtxsample \web\iis\extensions\formdump \web\iis\extensions\io\asyncread \web\iis\extensions\io\asyncwrite \web\iis\extensions\io\syncwrite \web\iis\progadmin\abo\enumeratekeys \web\networking\httpauth \winbase\debug\eventlog \winbase\eventtrace\tracedatahelper \winbase\indexing\smpfilt \winbase\msh\getproc \winbase\msh\stopproc \winbase\winnt\perfcounter \winbase\winnt\perftool\perfdlls\appmem\appdll \winbase\wtsapi\tssysinf\client \winbase\wtsapi\wtsapi \winui\auxillarydisplay\alarms \winui\auxillarydisplay\helloworld \winui\auxillarydisplay\pictures \winui\auxillarydisplay\tasks \winui\cursor \winui\globaldev\cssamp \winui\input\ime\multiui \winui\input\mouseinfo \winui\uiautomation\fragproviderunmgd \winui\uiautomation\simpleuiaprovider

 

 

6.6.4 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.6.5    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.

6.6.6  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.

6.6.7    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. To work around this issue, please use the supplied makefiles to build the samples.

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

6.6.8   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.

6.6.9  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.

6.6.10    Windows Communication Foundation sample setup may fail

Some of the WCF samples setup batch files use an obsolete environment variable name for the path to the SDK tools. Therefore, some sample setups may fail. This typically happens when setup requires one of the WCF SDK tools. This issue will be addressed in a future release. To work around this issue, add the following environment variable:

Variable name: WinSDK
Variable value: [SDK install path] (Example--C:\Program Files\Microsoft SDKs\Windows\v1.0)

6.6.11    Some Windows Presentation Foundation samples are not available in Allsamples.zip

The following three samples are not included in the sample archive for Windows Presentation Foundation samples that are otherwise found in the Allsamples.zip file. They include:

• hwnd in Windows Presentation Foundation
• Win32 Clock
• Host a Windows Presentation Foundation page in a Win32 Window

To obtain these samples, use the samples pages located under "Windows Presentation Foundation Samples" node in the Table of Contents. The Hwnd in Windows Presentation Foundation sample and Win32 Clock sample are located under the Application Samples node and the Host a Windows Presentation Foundation Page in a Win32 Window sample is located under the Technology Samples/Migration and Interoperability node. On these pages, click the Download icon to obtain the packaged complete sample source as a .ZIP file and save it locally.

6.6.12    Basic Ink Analysis sample fails to compile

The Basic Ink Analysis Sample located in \samples\TabletPC\BasicInkAnalysis\ fails to compile in this version of the Windows SDK. To work around this issue, manually replace the Results event and event handlers with the correct signature of ResultsUpdated and ResultsUpdatedEventHandler.

6.6.13    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.6.14  Some NetDS/Peer to Peer samples require changes to successfully compile

• Group Chat: In groupchat.h, please remove line 24 (#include pnrpns.h)
• PNRP: please make the following changes:

                1. In pnrp.h, change the following line from

                    BOOL VerifyPayloadData(__in PPEER_PNRP_ENDPOINT_INFO pEndpoint);

                to

                BOOL VerifyPayloadData(__in PPEER_DATA pData);\

               

                2. In pnrp.c, change line 236-237 from

                g_RegInfo.cbPayload = 0;

          g_RegInfo.pbPayload = NULL;

                to
                g_RegInfo.payload.cbData = 0;

          g_RegInfo.payload.pbData = NULL;

 

                3. Change line 514 from

                if (hr == HRESULT_FROM_WIN32(WSA_E_NO_MORE))

                to

                if (hr == PEER_E_NO_MORE)
 

                4. Change lines 821-824 from

                BOOL VerifyPayloadData(__in PPEER_PNRP_ENDPOINT_INFO pEndpoint)

          {

          PWSTR pwzTemp = (PWSTR) pEndpoint->pbPayload;

          ULONG cchTemp = pEndpoint->cbPayload / sizeof(WCHAR);
               

                to

                    BOOL VerifyPayloadData(__in PPEER_DATA pData)

          {

          PWSTR pwzTemp = (PWSTR) pData->pbData;

          ULONG cchTemp = pData->cbData / sizeof(WCHAR);
 

                5. Change line 887 from

                if (pEndpoint->cbPayload == 0)
                to

                if (pEndpoint->payload.cbData == 0)
 

                6. Change line 894 from

                if (VerifyPayloadData(pEndpoint))
                to
                if (VerifyPayloadData(&pEndpoint->payload))
 

                7. Change line 897 from

                (PWSTR) pEndpoint->pbPayload);
                to
                (PWSTR) pEndpoint->payload.pbData);