6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

This document specifies version-specific details in the Microsoft .NET Framework. For information about which versions of .NET Framework are available in each released Windows product or as supplemental software, see [MS-NETOD] section 4.

  • Microsoft .NET Framework 3.0

  • Microsoft .NET Framework 3.5

  • Microsoft .NET Framework 4.0

  • Microsoft .NET Framework 4.5

  • Microsoft .NET Framework 4.6

  • Microsoft .NET Framework 4.7

  • Microsoft .NET Framework 4.8

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1.6: Windows XP operating system Service Pack 2 (SP2) requires [XPCOM+]

Windows Server 2003 operating system with Service Pack 1 (SP1) requires [COM+] and Windows Server 2003 operating system with Service Pack 2 (SP2)

<2> Section 2.2.3.1.7: In Windows implementation, the dwVersionMax field of the Propagation_Token, as specified in [MS-DTCO] (section 2.2.5.4), is set to 3.

<3> Section 2.2.3.1.10: In Windows implementations, the following implementation-specific SOAP faults are generated.

  
 <xs:schema targetNamespace="http://schemas.microsoft.com/ws/2006/02/transactions"
       xmlns:mstx="http://schemas.microsoft.com/ws/2006/02/transactions"
       xmlns:xs="http://www.w3.org/2001/XMLSchema" 
       elementFormDefault="qualified">
       <xs:simpleType name="ErrorCodes">
             <xs:restriction base="xs:QName">
                   <xs:enumeration value="mstx:InvalidPolicy" />
                   <xs:enumeration value="mstx:CoordinatorRegistrationFailed" />
                   <xs:enumeration value="mstx:TooManyEnlistments" />
                   <xs:enumeration value="mstx:Disabled" />
             </xs:restriction>
       </xs:simpleType>
 </xs:schema>

InvalidPolicy: This error code is returned as a WS-AtomicTransaction Fault during two-phase commit processing.

CoordinatorRegistrationFailed:  This error code SHOULD be returned as a WS-AtomicTransaction Fault to a WS-Coordination Register SOAP message, if registration failed for an unspecified reason.

TooManyEnlistments:  This error code is returned as a WS-AtomicTransaction Fault to a WS-Coordination Register SOAP message, if the registration would have exceeded an implementation-specific maximum number of registered participants.

Disabled: This error code is returned as a WS-AtomicTransaction Fault to a WS-Coordination Register SOAP message, if the registration failed due to network transaction inbound/outbound restrictions.

<4> Section 3.1.4.2: In Windows, implementations, the OleTxTransactionHeader can be used if and only if an implementation of communication Mode value 0x01 (Singleton-Unsized) or Mode value 0x02 (Duplex) as specified by [MC-NMF] is used and the implementation is provided by NetFx versions 3.0 or 3.5.