Altium.Core.Diagnostics.ExceptionHandling

Configures the application exception logging state.

The configured exception logger factory.

Checks whether the exception logger factory is configured.

The configured exception filter factory. Default filter: , produced via .

Sets the global exception logger factory to the provided value.

The factory to use.

Sets the global exception filter factory to the provided value.

The factory to use.

Creates any filter that has a parameterless constructor.

The type of filter to create.

The instance to be used without DI.

The extensibility point that allows any global error-handling logic to ignore specific exceptions determined by the application at runtime.

Determines whether to log the exception.

The exception to inspect. If False, error handlers must not log the exception. Otherwise, it must be logged. This has no effect on exception handling.

Determines whether to suppress the exception.

The exception to inspect. If False, error handlers must not try to suppress the exception (if they can), passing it right through and potentially crashing the application. If True, error handlers must try to suppress the exception, if they are capable of it. If null, error handlers should decide by themselves how to proceed. This has no effect on exception logging.

Creates exception filters. If the filter does not have any parameters in the constructor and does not require custom initialization, consider using .

Provides an instance of an exception filter.

The default exception filter: logs everything and lets the handlers decide whether to suppress the exception.

The instance to be used without DI.

Handles the exceptions by logging their message using the provided logger. To configure the current AppDomain to use this method, invoke the method.

Constructor for the lazy instance and static context.

Constructor for DI.

The instance to be used without DI.

Provides the methods needed to setup AppDomain-level exception logging. Does not provide exception handling, i.e. the logged exceptions will still always be propagated.

Configures the current AppDomain to use custom exception logging. The exceptions are logged by the logger produced via the configured as long as they can be logged according to the configured .

Provides the methods needed to execute arbitrary logic with common exception handling.

Invokes the specified application bootstrap action, handling any exceptions that it might throw. The caught exceptions are logger into the logger produced by the configured .

The application bootstrap action to invoke. True if the invocation completed successfully. Otherwise, False. Will rethrow those exceptions that the configured explicitly forbids suppressing.

The bridging abstraction meant to decouple error handling from logging targets and other diagnostic libraries.

Consumers of this library are free to either implement this interface as a wrapper for their existing logging systems, or rely on the provided default implementation: .

Logs an exception with the specified message. The format and content of the final message are implementation-dependent.

The factory that the exception handling services use to create the exception logger.

Creates the logger. Can be a reusable single instance.

The default implementation of bridge: it only outputs the exception information into the standard error stream.

Before using custom loggers, consider capturing the standard error output of the application and sending it to the diagnostic storage, without any code on the application side.

The instance to be used as a parameter to the exception handling infrastructure.

Logs the exception into the standard error stream.

The prefix of an error message. The exception to be logged as a string.

The instance to be used without DI.