AsyncCausalityTracer.TraceOperationCreation Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Logs the creation of an asynchronous operation.
public:
static void TraceOperationCreation(CausalityTraceLevel traceLevel, CausalitySource source, Platform::Guid platformId, unsigned long long operationId, Platform::String ^ operationName, unsigned long long relatedContext); static void TraceOperationCreation(CausalityTraceLevel const& traceLevel, CausalitySource const& source, winrt::guid const& platformId, uint64_t const& operationId, winrt::hstring const& operationName, uint64_t const& relatedContext);public static void TraceOperationCreation(CausalityTraceLevel traceLevel, CausalitySource source, Guid platformId, ulong operationId, string operationName, ulong relatedContext);function traceOperationCreation(traceLevel, source, platformId, operationId, operationName, relatedContext)Public Shared Sub TraceOperationCreation (traceLevel As CausalityTraceLevel, source As CausalitySource, platformId As Guid, operationId As ULong, operationName As String, relatedContext As ULong)Parameters
- traceLevel
- CausalityTraceLevel
The trace level.
- source
- CausalitySource
The trace source.
- platformId
-
Guid
Platform::Guid
winrt::guid
Identifier for the operation type.
- operationId
-
UInt64
unsigned long long
uint64_t
An identifier for the asynchronous operation that's unique within the platform for the operation's lifetime.
- operationName
-
String
Platform::String
winrt::hstring
A human-readable description of the asynchronous work.
- relatedContext
-
UInt64
unsigned long long
uint64_t
Additional information related to this operation.
Remarks
Use the TraceOperationCreation method to log the creation of an asynchronous operation. An asynchronous operation represents a group of zero or more related synchronous work items that may be scheduled in an asynchronous way. Each asynchronous operation has a 128-bit GUID that identifies the operation type, like BCL task and WinJS Promise, and a UInt64 operation identifier that must be unique within the platform for the lifetime of the asynchronous operation. Good choices for operationId include a native pointer to an underlying object, or an integer that's incremented for each new operation. The operationName should be a human readable description of the asynchronous work. The relatedContext associates any additional information related to this operation.