Bilge

Bilge itself is the main trace library. The documentation here covers using the various features and functions of bilge.

Bilge Reference	Quick Links
Basic Logging	Tips: AutoTracing Unit Tests
Additional Options
Configuration Resolvers
Handlers

Basic Logging

Basic logging is what you will use most of the time. You can write out trace statements, timings and program flow using a variety of logging commands at different trace levels. See the following documentation: Basic Logging

Performance Considerations.

Tracing can take quite a bit of overhead and Bilge, by default, adds a lot of verbosity to the trace output, knowing how to configure Bilge and your trace statements efficiently can make a lot of difference to the performance of your trace code. Performant Logging

Transient Data

Occasionally you need data that transitions very quickly - there is a special implementation of transient data in Bilge which can be represented in flimflam. It is not a common scenario - see Using Transient Data

Actions

Actions are a specific use case - there are times when you need to know whether the code has done something, either for the point of view of testing or to be sure features are working as expected.
DocumentsNotImplementedException();

Utilities

DocumentsNotImplementedException();