Updated: July 19, 2016

Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista

The application provides the MSDTC Proxy with an ITipPullSink pointer when it calls on ITipHelper::PullAsync. The TM will in turn call on the ITipPullSink interface once the asynchronous pull operation completes.

System_CAPS_ICON_note.jpg Note

The TIP service feature is deprecated. The TIP service feature and all related APIs are available for use in the operating systems listed in the Requirements sections of the reference topics for those APIs. They might be unavailable in subsequent versions of the operating system. You might consider using the WS-AtomicTransaction (WS-AT) protocol as a replacement transaction coordination and propagation technology. WS-AT support is provided through Windows Communication Foundation (WCF) as part of the .Net Framework. For more information about WS-AT support in the .Net Framework see Transactions.

The application is responsible for implementing this interface. Applications are free to choose which objects implement it.

An application uses this interface to provide an ITipPullSink pointer.

ITipPullSink methodDescription
PullCompleteThe OLE Transaction manager calls on this method, once it has determined that the asynchronous pull operation has completed to return its completion status.

For an explanation of the requirement values, see Requirements (Component Services).

Platforms: Windows Server 2016, Windows 10, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista

Header: Declared in txcoord.h


Community Additions