Previous Topic: .NET Proxy ObjectNext Topic: Execution Methods

.NET Proxy › .NET Proxy Interface › .NET Proxy Object › Trace Control Methods

Trace Control Methods

There are five trace control methods. They are always generated with every .NET proxy object. These methods are used to start, stop, and write trace messages using the CA Gen trace capabilities.

Note: When used in this context, Trace refers more to runtime logging capability and you should not confuse this Trace with the Diagram Trace used to debug the generated action block logic.

The following table lists the five trace control methods:

Trace Control Method

Comments

StartTracing()

Turns on tracing with the output going to the file trace-<appname>-<procid>.out, where <appname> is the application name, and <procid> is the application's process id). This file is located in the

%USERPROFILE%\AppData\Local\CA\Gen xx\logs\net directory.

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

StartTracing(String filename)

Turns on tracing with the output going to a file specified by the filename parameter.

StartTracing(TextWriter writer)

Turns on tracing with the output going to the TextWriter parameter passed in.

TraceOut(String message)

Writes the message to the trace output if tracing is enabled at that time. If tracing is not enabled, the method simply returns.

StopTracing()

Turns off all tracing.

Tracing in CA Gen runtime is global in scope. If one proxy turns Tracing on, it is enabled for all the proxies running in the same process.