2.2.1.1.1 Version-Specific Aspects of Connection Types Relevant to an Application

The following table shows version-specific aspects for connection types that are relevant to applications. This table includes connection types and messages that are supported on certain versions as well as messages whose size is version specific. If a connection type or message that is relevant to applications is omitted from this table, it is not version specific and MUST be supported on all versions.

Version-specific aspect	V1	V2	V4	V5	V6
Version supports connection type CONNTYPE_TXUSER_BEGIN2 (section 2.2.8.1.2 ).	No	Yes	Yes	Yes	Yes
Version supports connection type CONNTYPE_TXUSER_EXTENDEDWHEREABOUTS (section 2.2.8.2.2.1 ).	No	No	No	Optional <3>	Optional <4>
Version supports connection type CONNTYPE_TXUSER_GETSECURITYFLAGS (section 2.2.8.4.1 ).	No	No	Yes	Yes	Yes
Version supports connection type CONNTYPE_TXUSER_IMPORT2 (section 2.2.8.2.2.5 ).	No	Yes	Yes	Yes	Yes
Version supports connection type CONNTYPE_TXUSER_PROMOTE (section 2.2.8.1.3 ).	No	No	No	Optional <5>	Optional <6>
Version supports connection type CONNTYPE_TXUSER_SETTXTIMEOUT (section 2.2.8.3.3 ).	No	Optional <7>	No	No	No
Version supports connection type CONNTYPE_TXUSER_SETTXTIMEOUT2 (section 2.2.8.3.4 ).	No	No	Optional	Optional <8>	Optional <9>
Version supports connection type CONNTYPE_TXUSER_TRACE (section 2.2.8.3.5 ).	No	No	Yes	Yes	Yes
Version supports messages TXUSER_EXPORT_MTAG_CREATE2 (section 2.2.8.2.2.2.2 ) and TXUSER_EXPORT_MTAG_CREATE_NET_TX_DISABLED (section 2.2.8.2.2.2.4 ).	No	No	Yes	Yes	Yes
Version supports message TXUSER_RESOLVE_MTAG_ACCESSDENIED (section 2.2.8.3.2.1 ).	No	No	Optional <10>	Yes	Yes
The SourceTmAddress field is described by the structure NAMEOBJECTBLOB (section 2.2.5.3 ) in message TXUSER_ASSOCIATE_MTAG_ASSOCIATE (section 2.2.8.2.1.1.1 ).	Yes	No	No	No	No
The SourceTmAddress field is described by the structure OLETX_TM_ADDR (section 2.2.4.2 ) in message TXUSER_ASSOCIATE_MTAG_ASSOCIATE (section 2.2.8.2.1.1.1 ).	No	Yes	Yes	Yes	Yes
The SourceTmAddress field is described by the structure NAMEOBJECTBLOB (section 2.2.5.3 ) in message TXUSER_EXPORT_MTAG CREATE (section 2.2.8.2.2.2.1 ).	Yes	No	No	No	No
The SourceTmAddress field is described by the structure OLETX_TM_ADDR (section 2.2.4.2 ) in message TXUSER_EXPORT_MTAG_CREATE (section 2.2.8.2.2.2.1 ).	No	Yes	Yes	Yes	Yes
The grfNetworkDtcAcess field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG bits: DTCADVCONFIG_ NETWORKDTCACCESS_ENABLE DTCADVCONFIG_ NETWORKDTCACCESS_ADMIN DTCADVCONFIG_ NETWORKDTCACCESS_TX DTCADVCONFIG_ NETWORKDTCACCESS_CLIENTS DTCADVCONFIG_ NETWORKDTCACCESS_TIP	No	No	Yes	Yes	Yes
The grfNetworkDtcAcess field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG bits: DTCADVCONFIG_INBOUNDNETWORK_TX DTCADVCONFIG_ OUTBOUNDNETWORK_TX DTCADVCONFIG_ SECURITYLEVEL_NOSECURITY DTCADVCONFIG_ SECURITYLEVEL_AUTHENTICATEDONLY DTCADVCONFIG_ SECURITYLEVEL_MUTUALAUTH	No	No	No	Yes	Yes
The grfOptions field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG_OPTIONS bits: DTCADVCONFIG_OPTIONS_LUTRANSACTIONS_DISABLE	No	No	No	No	Yes
The guidSignature field in the STxInfo structure present in propagation-related messages uses a reserved GUID with the binary value representation of {2adb4463-bd41-11d0-b12e-00c04fc2f3ef}.	No	Yes	Yes	Yes	Yes
The STxInfo structure supports versioning based on its guidSignature field.	No	Yes	Yes	Yes	Yes
Version supports connection type CONNTYPE_TXUSER_EXPORT2	No	No	No	No	Yes
Version supports message TXUSER_EXPORT_MTAG_EXPORT_COMM_FAILED	No	No	No	No	Yes