Release Notes for the Microsoft Windows Code-Named "Longhorn" SDK


Welcome to the Developer Preview Edition of the Microsoft Windows Code-Named "Longhorn" Software Development Kit (SDK). The "Longhorn" SDK contains documentation, samples, command-line compilers, and tools designed to help you develop applications and libraries that target the Windows Code-Named "Longhorn" operating system.

Please note that this release is for preview purposes only. The APIs, documentation, samples, and tools provided in this release are preliminary and subject to change.

Because this is a pre-release edition, many known issues are identified in this document. Please read the installation instructions and known issues before installing. See the "Longhorn" Developer Center and check the "Longhorn" Beta Newsgroups for updates to known issues.

NOTE: This document will be updated as new issues are discovered. New entries will be identified by "(New: date added)" at the end of the heading for the entry.

Your feedback is important to us. Please use the Feedback links at the bottom of each topic to provide constructive information that we can use to improve the content. Your participation and feedback through the "Longhorn" Beta Newsgroups is also appreciated.

For additional information about "Longhorn", see The MSDN online "Longhorn" Developer Center. The "Longhorn" Developer Center is focused on keeping developers up-to-date on how they can take advantage of "Longhorn's" rich new client features in their applications. Visit the "Longhorn" Developer Center often to see new articles, read monthly columns, participate in the "Longhorn" newsgroups, download sample code, and read the Editor's Web Log.

--------------------------------------------------------------------------------

Instructions for Installing "Longhorn," Visual Studio "Whidbey," and the "Longhorn" SDK
To build "Longhorn" applications, it is essential that you install the components on the "Longhorn" DVD in a specific order. Please read the following installation instructions carefully:

From the "Longhorn" DVD, install the "Longhorn" operating system.
Optional: From the "Longhorn" DVD, install Microsoft Visual Studio "Whidbey" Alpha, accepting the default options.
From the "Longhorn" DVD, install the "Longhorn" SDK.
Follow the instructions in the "Longhorn" SDK Setup wizard, accepting the default options.
To have your environment variables recognized, you must restart your computer.


--------------------------------------------------------------------------------

Known Issues
This release has the following known issues. For additional information about "Longhorn", see The MSDN online "Longhorn" Developer Center.

"Longhorn" SDK Issues
Setup and Installation Issues
Installing the Microsoft .NET Framework SDK and the "Longhorn" SDK on the same computer is not supported at this time. The documentation for the .NET Framework SDK is included in the "Longhorn" SDK.
Platform SDK samples are not contained in this release of the "Longhorn" SDK, which contains samples demonstrating new "Longhorn" functionality that are intended only for "Longhorn".
Samples demonstrating Windows functionality from the Microsoft Windows Server 2003 family and earlier can be found in the Platform SDK, which can be installed at http://www.microsoft.com/msdownload/platformsdk/sdkupdate/.
Documentation: Classes usable as "Longhorn" markup language elements are not properly displayed
In the WinFX SDK reference documentation, classes that are usable as "Longhorn" markup language (code-named "XAML") elements are not properly displaying a valid markup syntax in their class reference pages. To discover which classes can be used as "XAML" elements, use the "XAML" schemas that are integrated into the Visual Studio "Whidbey" Alpha development environment when developing your "Longhorn" application. IntelliSense, code validation, or reading the schema directly can all be used to inform you which classes are actually valid "XAML" elements.

SDK Tools: Tracewpp processing fails
Before compiling the source files, you must run the preprocessor, TraceWPP, on each source file. To run the preprocessor on TraceExampleApp, use the following command:

tracewpp -cfgdir:%MSSdk%\bin\wppconfig\rev1 example1.c example2.c


Samples and Build Environment not supported on Microsoft Windows XP or Windows Server
In this release, the "Longhorn" SDK samples and build environment are supported only on "Longhorn". It is recommended that you use these components only on "Longhorn" with the appropriate setup configuration.

Samples: Building samples with MSBuild
When a sample page in the documentation says to build a sample using the following command line:

msbuild [filename]

[filename] can either be a .csproj or a .vbproj file. Alternatively, if the csproj or .vbproj file are located in the current directory, then you can just type MSBuild without specifying a project filename.

For more information about using MSBuild, see the "Building from the Command Line" section in the topic "About Creating, Building, Deploying, and Launching Applications" in the "Longhorn" SDK documentation.

Samples: Some samples require Visual Studio to be installed in order to build
Some samples shipped with the "Longhorn" SDK have a dependency on Visual Studio to be installed in order to build. If installing Visual Studio, it must be installed prior to installing the "Longhorn" SDK.

Samples: Registry Key issues when Visual Studio is not installed
If you have installed the "Longhorn" SDK without installing Visual Studio, then you need to create a registry entry. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework, create an entry called sdkInstallRootv1.2 under and set its value to the install location of the "Longhorn" SDK (including a trailing "\"). For example, if you installed the "Longhorn" SDK to "C:\Program Files\Microsoft Longhorn SDK", then the string value for sdkInstallRootv1.2 would need to be set to C:\Program Files\Microsoft Longhorn SDK\. Caution should always be used updating the Registry.


Samples: For C++ samples developed in Visual Studio, set include and lib paths in the Visual Studio IDE
When developing a C++ sample using Visual Studio and the "Longhorn" SDK, you need to set the include and lib path in the Visual C++ IDE to the "Longhorn" SDK include and lib paths respectively to ensure the "Longhorn" SDK headers and libraries are found and used. To change these directory paths inside the Visual Studio IDE when developing with C++, from the Tools menu, select Options. In the resulting dialog box, select Projects and then VC++ Directories. Add the "Longhorn" SDK include and lib directories.

Samples: Issues with Core Services SDK
Simple_command.exe and Command_with_handler.exe samples and their associated .deploy samples fail to run. To run Simple_command.exe and Command_with_handler.exe, copy the PresentationFramework.dll into the same folder as the .EXE. There is no current workaround for the .deploy failure.

Samples: PrintContext sample fails if a printer is not installed
If a printer is not installed, the PrintContext sample fails when attempting to print. Workaround: Add a printer to your system (you must have a local or network printer available). From the Start menu, choose Settings, and then choose Printers and Faxes. On the File menu, choose Add New Printer and follow the wizard instructions.

Samples: Issues with samples that use the Video element
There are issues with "Avalon" samples that use Video Element and require you to have a video card that supports hardware acceleration. See the "Longhorn" operating system release notes for information about hardware requirements.

In the Login Screen sample, video performance might degrade with repeated use. This is due to an issue with the Video element in "Longhorn." To work around this issue, restart the sample.

In the Channel Surfin sample, you might sometimes hear the volume for the preview video over the volume of the main video. This is due to an incompatibility between the Video element in "Avalon" and the audio engine in this release of "Longhorn."

Samples: PageFunction issue impacts SimpleIUI2 SDK sample
The Application Services sample "SimpleIUI2," which demonstrates the use of the PageFunction class, runs but is not fully functional. A PageFunction normally fires a NonGenericReturn event when OnFinish is called so that the PageFunction can return a value to its caller. However, due to a known issue, the PageFunction class does not currently generate NonGenericReturn events.

In the sample, clicking the Back button in Task1 should return you to the first page and display a new string, but only the navigation occurs; no new string is displayed. To work around this issue, use the Application.Properties collection to pass information between pages.

Samples: ListSignatures do not run in Visual Studio
The ListSignatures SDK samples for Visual Basic .NET and C# do not run from within Microsoft Visual Studio. To work around this issue, compile these samples from the command line using the following command:

msbuild -t:cleanbuild
To compile the ListSignature sample, you must have a certificate that can be used for digital signatures. If you do not have a valid certificate, the sample will not build. You can obtain certificates from a certificate authority such as VeriSign, Inc.

To run the compiled application, type the following:

For the Visual Basic .NET sample: bin\release\ListSignatures_vb.container
For the C# sample: bin\release\ListSignatures_cs.container
Samples: "Indigo": Internet Connection Firewall (ICF) causes network communication to fail
The IFC is enabled by default. Enabling ICF blocks incoming connections to the computer it's running on, except when the connection originates from the same computer and is targeted at "localhost" or "127.0.0.1". This causes many "Indigo" applications to fail. For example, this issue causes the Reliable Messaging sample named "Hello" to hang.

If client and server are running on the same computer, make sure that both the client and server bind their port to localhost. If they are not running on the same computer, use the computer's name when creating the port (on both the client and the server computers), and enable communication on the IP ports that your application is using (on both the client and server) by adding them as services which are accessible from other computers. For debugging purposes, you might want to temporarily disable the ICF.

Samples: "Indigo": Internet Connection Firewall (ICF) causes samples using DTC to fail
The Internet Connection Firewall (IFC) is enabled by default. Enabling ICF will cause the transaction sample "EnlistDistTx" and the Reliable Messaging sample "Durable" to fail with the exception:

System.Runtime.InteropServices.COMException (0x8004D00E): The transaction has already been implicitly or explicitly committed or aborted

The ICF is working as designed and is blocking incoming messages. However some "Indigo" samples require two way communication on the network. The ICF can be configured to allow incoming messages on certain ports. To work around this issue, configure DTC to work through a firewall. To do this, follow the instructions in Knowledge Base article 250367.

Samples: Remoting: Internet Connection Firewall (ICF) causes some samples to fail
The Internet Connection Firewall is enabled by default. With the ICF enabled remoting applications will fail to work across computers (or even on the same box when 'localhost' is not used), unless a port is opened in the ICF. To work around this issue, explicitly open ports in the ICF to allow for communications from client to server in accordance with the remoting configuration.


Samples: Unified Service Discovery and Publication (USDP) samples have incorrect documentation
Three of the OPath samples in the "Using Unified Service Discovery and Publication API" topics are incorrect. To work around this issue, use the following queries instead of those in the documentation.

In the Active Directory samples, the following example:

Printer[ supportsColor = true && ( printerName like 'Home' or name like 'Work' ) ]
Service[ ServiceInterface=ServiceConnectionPoint]

should read:

Printer[ printColor = true && ( printerName like 'Home' or name like 'Work' ) ]
Service[ ServiceInterface = 'ServiceConnectionPoint' ]

In the SSDP examples, the following example:

Service[ ServiceType = Castle]

should read:

Service[ ServiceType = 'Castle' ]

Executing the original OPath queries may generate exceptions or return no results.

Samples: Manifest must be registered before running WMI.Configuration sample
Before running each of the WMI.Configuration samples, the manifest file (.man) that is downloaded with the sample must be registered. If the sample is run without registering the manifest, the sample will fail with an error.

The manifest file can be registered as follows on the command line:

wcmcompile wcmsample1.man (wcmcompile.exe can be found in the "%windir%\system32\wmi config" folder)

These sample build issues should be resolved, however they will not make it into the coming RC1 build of the LHSDK; therefore adding instructions to fix these 2 known samples:

Samples: Hello "Longhorn" Help C# sample and TxtViewer NGSCB sample require project file updates
The Hello "Longhorn" Help sample, written in C#, needs to have its project file updated in order to properly build. The fix is to edit HelloHelpLHCS.csproj and change the line:

<Item Type="Reference" Include="System.Help.Pane" HintPath="$(windir)\Microsoft.NET\Framework\v1.2.30703\System.Help.Pane.dll" Name="System.Help.Pane" />

to

<Item Type="Reference" Include="System.Help.Pane" HintPath="$(windir)\Microsoft.NET\Windows\v6.0.4030\System.Help.Pane.dll" Name="System.Help.Pane" />

The TxtViewer NGSCB sample needs to have its project file updated in order to properly build. The fix is to edit TxtViewer.csproj and change the line:

<Item Type="Reference" Include="System.Security.TrustedPlatformServices" Name="System.Security.TrustedPlatformServices" />

to

<Item Type="Reference" Include="System.Security.TrustedPlatformServices" HintPath="$(windir)\ngscb\System.Security.TrustedPlatformServices.dll" Name="System.Security.TrustedPlatformServices" /

Samples: C# version of SpeechRecognition sample has project file error
The C# version of the SpeechRecognition sample has a typo in its project file (SpeechRecognition.csproj) that prevents the sample from building. The following line:

<Item Type="Reference" Include="System"Name="System" />

should read

<Item Type="Reference" Include="System" Name="System" />

Samples: WMI LogicalDrive sample has incorrect build steps
The Visual Basic .NET version of the LogicalDrive (Visual Basic .NET) sample has incorrect information in the build steps. The following instructions:

Run "sn.exe /k TestPublicKey.snk"
Add the following lines to the .cs file: Imports System.Reflection;
Build the sample
should read

Run "sn.exe /k TestPublicKey.snk"
Add the following lines to the .vb file: Imports System.Reflection; <assembly: AssemblyKeyFile("TestPublicKey.snk")>
Build the sample
Samples: Peer-to-Peer and PNRP networking samples do not run without Peer-to-Peer component installed
The Peer-to-Peer and PNRP networking samples require the Windows Optional component Peer-to-Peer. To install this component, from Add or Remove Programs, select Add Windows Components, and select Peer to Peer.

Samples: Explorer sample .deploy file fails to run (New: October 27, 2003)
The .deploy file for the Explorer SDK sample fails to run. To run the sample, use the .exe file instead.

Samples: Some makefiles are incorrect (New: October 27, 2003)
If the makefile supplied with a sample does not seem to work, the sample might only compile in the Visual Studio IDE. The following samples need to be build using the Visual Studio IDE environment instead of using the supplied sample makefiles (.mk extension).

Hello "Longhorn" Help (Visual Basic .Net)
EventLog - QueryLog (C++)
WMI.Configuration Sample1 (C++)
WMI.Configuration Sample2 (C++)
WMI.Configuration Sample3 (C++)
Media Services Console Player (C#)
Media Service Metadata Viewer (C#)
Media Services Media Player
Managed Media Services Publish Media Sample
GUI to Add, Update, Delete, Find Persons via Identity and Principal
Import/Export Identity Card Utility
Samples: Some C# and VB project files contain an incorrect "HintPath" setting (New: October 27, 2003)
Some C# and Visual Basic .NET project files (.csproj and .vbproj respectively) contain an incorrect "HintPath" setting that prevents the sample from being built on the command line with msbuild. These samples do build inside the Visual Studio IDE however.

To resolve the HintPath, change

HintPath="..\..\Windows\"

to

HintPath="$(windir)\"

General Issues
Remoting: SSL-enabled applications will fail when security protocol is not set
Secure channel scenario fails with an "Invalid token" exception from the server side, which translates to a "remote side has dropped the stream" exception on the client side.

To work around this issue, specify the security protocol (such as SSL3, SSL2) using the securityProtocol settings in the TcpChannel properties bag or using the <channel> element in the TcpChannel settings in the configuration file. For example:

<channel id="tcps" type="System.Runtime.Remoting.Channels.Tcp.TcpChannel" secure="true" certificateFile="" requireClientCertificate="false" securityProtocol="SSL3" checkRevocation="false"/>

System.Net: Applications using the SslStream class without setting the security protocol fail
The application fails with an "Invalid token" exception from the server side. To work around this issue, specify a security protocol other than Default (such as SSL3, SSL2) in the SslStream class constructor.

Microsoft Assistance Markup Language (MAML) schema files
The MAML schema consists of a set of .xsd files that are used to create and validate "Longhorn" Help content. Maml.xsd is the root-level file that should be referenced for validation. The files can be found in the following locations:

On the "Longhorn" SDK disc at E:\misc\MAML_Schema\ (where E: is the drive letter)
Installed with the "Longhorn" SDK at: C:\Program Files\Microsoft Longhorn SDK\misc\MAML_Schema
"WinFS": System.Storage.Base schema merged into System.Storage namespace
The System.Storage.Base schema has been merged into the System.Storage namespace. Data classes previously defined in System.Storage.Base are now in the System.Storage namespace. In the documentation, data class names in the form of "System.Storage.Base.*" should be substituted with "System.Storage.*".

Assemblies for Desktop Programming are not in expected location
Certain assemblies used for desktop programming applications - System.Windows.Explorer.dll, System.Windows.Contacts.dll, and System.Windows.Contacts.Interop.dll - are located in the %windir%\microsoft.net\avalon directory.

If you delete these assemblies from your Visual Studio project and need to create new references to them, or if you create your Visual Studio project without using one of the "Longhorn" templates in the New Project dialog box, the assemblies will not appear in the Add Reference dialog box.

To work around this issue, for C# or Visual Basic .NET projects, do the following: On the Project menu in Visual Studio, click Add Reference. In the Add Reference dialog box, click Browse and browse to that directory to find and add these references. If the directory does not appear in this dialog box, switch the View mode to Details to see it.

Information available on Visual Studio .NET project templates
To learn more about Visual Studio .NET project templates, create a new Visual Basic .NET, C#, or "Longhorn" project. The Solution Explorer lists all files that your project contains. To learn more about the project template, right-click Readme.html and choose View in Browser.

Capitalization requirement for debugging with C# projects in Visual Studio .NET
Debug output will not work in C# code-behind files that use a #define Debug statement unless the namespace names are fully qualified in the Debug.WriteLine call, as in:

System.Diagnostics.Debug.WriteLine("Output to the debug console");

To work around this issue, use #define DEBUG (all uppercase) if you want to use unqualified namespace names, as in:

Debug.WriteLine("Output to the debug console");


Unable to Create "Longhorn" Rights Management Protected documents using the Windows Client Printer driver
The Rights Management client is included in "Longhorn," but the Rights Management environment needs to be configured before the Windows Client Printer Driver can use it. If the environment is not properly configured, the Windows Client Printer Driver will fail without generating the Rights Management protected document, and with no error to indicate the failure.

To work around this issue, set up your development environment as follows.

The Windows Client Printer Driver needs a Microsoft Windows RMS server available to use for licensing and certification. The Windows RMS server provides certificates and licenses to clients in a Rights Management system.

You should set up a Windows RMS server that uses the pre-Production hierarchy, or ensure that you have access to an RMS server in the pre-Production hierarchy. Windows RMS is an optional component for the Windows Server 2003 family of operating systems. If you need to install Windows RMS on a server, you can download it from the Microsoft Web site.

Server Configuration. After installation of Windows RMS but before provisioning the service, you must add the following registry keys and string values in the server under HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\1.0. After adding these registry keys, be sure to restart IIS and close the browser window.

UddiProvider = "0e3d9bb8-b765-4a68-a329-51548685fed3" When you want to switch to the Production chain, you should remove this key.
If another RM service is already deployed in Active Directory, add this empty key: GICURL = "".
Client Configuration. In a Rights Management system, clients query Active Directory to discover the location of activation, certification, and licensing services on their network. To force your application to find a specific service URL, add the appropriate registry key from the following list, along with the URL as a string value called (default).

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\ServiceLocation\Activation
This registry key holds the URL of the machine activation and user certification service.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\ServiceLocation\EnterprisePublishing
This registry key holds the URL of a service that signs publishing licenses within an enterprise network.
Installing the Windows Client Printer Driver. The Windows Client Printer Driver enables you to create "Longhorn" Rights Management protected documents. Because it is not installed by default, you must follow these steps to install it:

Open the Control Panel.
Click Add/Remove Programs.
Click Add/Remove Windows Components (left panel of the window).
Select Windows Client Printer Driver.
Click Next.

Presentation subsystem (code-named "Avalon")
"Avalon" Media Services might stop responding
Applications that use "Avalon" audio or video controls might stop responding if the audio controller is disabled or not properly installed. The situation can occur when you run an audio or video application or attempt to change states such as Resume, Seek or Begin, or End. To work around this issue, install drivers for the audio controller and ensure it is working properly.

Console I/O in applications that use "Avalon" can have unexpected behavior
Code-only applications that use "Avalon" contain .csproj project files that specify either of the following final target types:

<Import Project="$(LAPI)\WindowsApplication.target" />
<Import Project="$(LAPI)\WindowsDocument.target" />
If these applications use Console I/O, they can fail at run time or have unexpected behavior. Console.WriteLine calls might not show output. Console.ReadLine calls might fail with an unrecoverable exception.

To work around this issue, avoid using Console I/O in these applications, if possible. Instead, you can use the DockPanel class and add new Text elements to the panel for each line that you would otherwise have output with Console.WriteLine. You can also use the TextBox element where you would otherwise have input text with Console.ReadLine. For a representative example of how to work around using direct Console I/O, see the SDK Accessibility sample "Find and Invoke the Start Menu."

IntelliSense not working well for Style tag
If you are using Visual Studio .NET to edit an .xaml file, IntelliSense will not work well inside the Style tag. A fix is under investigation; see Late Breaking Issues at http://go.microsoft.com/fwlink/?LinkId=20186 for possible fixes.

To workaround this issue, you can change the file extension from .xaml to .xml. This will activate IntelliSense within the Style tag. When you no longer need this workaround, rename the extension back to .xaml.


Communications subsystem (code-named "Indigo") Issues
Web services specifications implemented by the PDC 2003 version of "Indigo"
This version of "Indigo" implements several Web services specifications, many of which are draft versions of work in progress. This version of "Indigo" is an early technology preview and its implementation of these specifications is subject to change as the specifications evolve.

Additional setup steps required for using transactions
Using WS Transactions requires additional setup. When you need to protect the transmission of a reliable message with a transaction or propagate a transaction from a caller to the service, you will need to run Fixfx.bat to enable this transaction functionality. This functionality is also needed when marshaling transactions using the System.Transactions API.

To work around this issue, download the MarshalTx or ExplicitTm "Indigo" samples from the "Longhorn" SDK. Both of these samples include a batch file named Fixfx.bat. Open a "Longhorn" Build Environment command prompt and run this batch file to perform the additional setup steps.

Cassini is not supported in this release
"Indigo" .MSGX files do not work with Cassini in this release of "Longhorn". To enable execution of .MSGX files, the file must be served by Internet Information Services (IIS).

Windows security requires domain user
When using Windows security (including impersonation) in "Indigo" applications, the process must be running using a domain user account. Running with local accounts (even Administrator) will fail with a System.MessageBus.Security.MessageSecurityException. To work around this issue, log in as a domain user before running an "Indigo" application that uses Windows security.

Enabling "Indigo" Security within a workgroup
If your computer belongs to a workgroup but does not belong to a Microsoft Windows domain, all applications built using "Indigo" that both load the default SecurityManager and the "main" ServiceEnvironment will generate an exception containing the message "Cannot enumerate trusted domains" and fail to run. This behavior occurs because the SecurityManager in the "main" ServiceEnvironment requires all senders to authenticate with a Microsoft Windows domain by default. Your application will generate an exception even if it uses other forms of authentication, such as X.509 or username and password.

To run applications that load the SecurityManager from the "main" ServiceEnvironment in a workgroup environment, you must modify the Machine.config file to remove the domain dependency. Note that even after you do this, applications that expressly authenticate users using a Microsoft Windows domain will fail because there is no domain available to perform authentication.

As a result, all samples in the Secure and Secure/Advanced folders will fail if your computer is not associated with a domain. However, after you modify the Machine.config file, all samples will run except the following:

Secure\AdvancedTopics\Impersonation
Secure\SimpleWindowsAuthRequestReply
Secure\WindowsAuthHelloSession
Secure\WindowsAuthRequestReply
To allow security samples to run from a workgroup do the following steps:

Open the Machine.config file in the folder that contains the runtime version used by the "Indigo." This file has the following path: <WindowsRoot>Microsoft.NET\\CONFIG\Machine.config
Locate the configuration that describes the main ServiceEnvironment:
<serviceEnvironments>
<serviceEnvironement name="main">
...

Within the main ServiceEnvironment definition, remove the definitions of the windows, windowsWithLicensing, and windowsUsingSspi profiles. Find and remove all of the following child elements:
<windows>
</windows>
<windowsWithLicensing>

</windowsWithLicensing>
<windowsUsingSspi>

</windowsUsingSspi>

Within the main ServiceEnvironment definition, find the <applicationSecuritydefaultBinding= "windows"> element and change it to <applicationSecuritydefaultBinding="userNamePassword">.
Interop with ASP.NET Web Services
To consume an "Indigo" Web Service from Add Web Reference or Wsdl.exe, the "Indigo" service must be using Datagrams over HTTP. Dialogs and/or TCP are not supported by wsdl.exe and Add Web Reference. Additionally, in order for an "Indigo" client to consume ASP.NET Web Services, the "Indigo" client must have policy application turned off.

Using TCP to invoke a hosted .msgx service
Using TCP to invoke a hosted .msgx service requires a manual change to the TCP Transport Listener. To use TCP with a hosted .msgx service, modify the TCP Transport Listener to run with "Network Service" by typing the following command:

sc config tcptransportlistener obj= "NT AUTHORITY\NetworkService" password= ""

Reliable messaging exceptions
Exceptions can be raised during message processing by the message processing code on which the Reliable Messaging feature is implemented. These exceptions are not handled by the Reliable Messaging infrastructure. In some instances, these exceptions may appear in your code or dialog boxes. To work around this issue, catch these exceptions in your application.

Next Generation Secure Computing Base (NGSCB) Issues
FontFamily Attribute must be set in some TSPIDL files
If your Trusted Service Provider Interface Definition Language file includes an element that displays text or serves as a parent to an element that displays text, you must set the FontFamily Attribute to "Verdana" or "Georgia" in the outermost element in the file. Failure to do so may result in unexpected behavior.


-------------------------------------------------------------------------
Copyright © 2002-2003 Microsoft Corporation. All rights reserved.

MSDN