6. Known Issues

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

6.1 Setup and General Development

6.2 Headers and Libraries

This section describes known issues with headers and libraries included in the Windows SDK and offers possible workarounds.

6.2.1    Using the Windows SDK to develop Win32 C++ applications with Visual Studio 2005 requires a workaround

There is a known issue with adding the Windows SDK library and include path information to the user's Visual Studio 2005's directory paths. Using the Windows SDK to develop Win32 C++ applications with Visual Studio 2005 requires the following workaround. To work around this issue, manually add the path to the Visual Studio 2005 path information.

NOTE The path given assumes the Windows SDK was installed on your C drive. Please change appropriately.

1. Start Visual Studio 2005.
2. From the Tools menu, click Options, click Projects and Solutions, and then click VC++ Directories.
3. In the "Show Directories for:" drop-down list, select Include Files.
4. Include the following by selecting each of these directories by using the up arrow button to move them to the top of the list:
   • C:\Program Files\Windows SDKs\Windows\V1.0\VC\INCLUDE
   • C:\Program Files\Windows SDKs\Windows\V1.0\VC\INCLUDE\SYS
   • C:\Program Files\Windows SDKs\Windows\V1.0\INCLUDE
   • C:\Program Files\Windows SDKs\Windows\V1.0\INCLUDE\GL
5. Select the following Library Files from the "Show Directories for:" drop-down menu by using the up arrow button to move them to the top of the list:
   • C:\Program Files\Windows SDKs\Windows\V1.0\VC\LIB
   • C:\Program Files\Windows SDKs\Windows\V1.0\LIB
6. Select OK.

6.3 Compilation Tools

The following section describes known issues with compilers and offers possible workarounds.

6.4 SDK Tools

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    Known issues with Windows Communication Foundation tools

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

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.

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.
• 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.  To work around this issue, 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.4    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).

• 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.5 Documentation

6.5.1    Copy Code sometimes produces an error

When trying to view source code for some WinFX samples in the documentation, a script error may appear when trying to use the Copy Code button.  To work around this issue, copy the code using <Ctrl>+<C> and paste it using <Ctrl>+<V>.

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

When navigating to a some documentation topics using the Table of Contents, Index, Search, or links, the topic will appear with an Internet Script Error indicating that an error has occurred in the script on the page. To work around this issue, click No to continue and the topic will appear. This issue will be addressed in a future release.
 

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)	Graph Calc (C# only) HostingAxInWpfWithXaml (XAML) Tab Control Styles (VB only) Window Move (C# and VB)	Data Binding in a WPF Client WPF Rich Client with a WCF Service SecureBroadcast Peer Channel Broadcast Typed Proxy Sample (VB only) WMI Provider Sample (VB only) End to End Tracing Sample (VB only) Transaction Behavior (compiles, doesn't run cross-machine) XML Formatter (compiles, doesn't run cross-machine) Operation Requirement (compiles, doesn't run cross-machine) Federation (C# only) Http Binding User Name Over Certificate ETWTracing (VB only)	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    SDK samples require full read/write access

When building samples that are shipped in the SDK, copy the entire sample to a directory in your local environment in which you have full read/write access.  There is no known workaround for this issue.

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    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. To work around this issue, hand-generate the configuration file for the client or use the configuration file provided in the sample.

6.6.11    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.12    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.13    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.