MethodCallTargetBase Class

Initializes a new instance of the MethodCallTargetBase class.

Gets a value indicating whether the target has been initialized.

Gets the logging configuration this target is part of.

Gets or sets the name of the target.

Gets the array of parameters to be passed.

Gets the object which can be used to synchronize asynchronous operations that must rely on the .

Closes the target to release any initialized resources

Closes the target.

Releases unmanaged and - optionally - managed resources.

Calls the target method. Must be implemented in concrete classes.

Calls the target DoInvoke method, and handles AsyncContinuation callback

Calls the target DoInvoke method, and handles AsyncContinuation callback

Flush any pending log messages (in case of asynchronous targets).

Flush any pending log messages

Initializes the target before writing starts

Calls the Precalculate(LogEventInfo) on each volatile layout used by this target. This method won't prerender if all layouts in this target are thread-agnostic.

Renders the logevent into a string-result using the provided layout

Renders the logevent into a result-value by using the provided layout

Resolve from DI ServiceRepository

Returns a string that represents the current object.

Prepares an array of parameters to be passed based on the logging event and calls DoInvoke().

Writes an array of logging events to the log target. By default it iterates on all events and passes them to "Write" method. Inheriting classes can use this method to optimize batch writes.

Writes logging event to the target destination

Writes the log to the target.

Writes the array of log events.

Writes the array of log events.

Writes a log event to the log target, in a thread safe manner. Any override of this method has to provide their own synchronization mechanism. !WARNING! Custom targets should only override this method if able to provide their own synchronization mechanism. Layout-objects are not guaranteed to be thread-safe, so using them without a SyncRoot-object can be dangerous.

Writes an array of logging events to the log target, in a thread safe manner. Any override of this method has to provide their own synchronization mechanism. !WARNING! Custom targets should only override this method if able to provide their own synchronization mechanism. Layout-objects are not guaranteed to be thread-safe, so using them without a SyncRoot-object can be dangerous.

LogEvent is written to target, but target failed to successfully initialize