The ErrorUnit namespace contains classes for attaching loggers and IoC dependency injection libraries; to ultimately log errors in a format ErrorUnit can convert to unit tests. Follow the links to see how to set up each.

ErrorUnit works by intercepting calls, and on error logging them; To that end you will need to set up the means of call interception. There are three call interceptor types that you should use when applicable; ErrorUnitMvcActionFilterAttribute that adds interception to MVC Controllers, ErrorUnitWebApiActionFilterAttribute that adds interception to Web API Controllers, and most importantly an ErrorUnit compatible IOC Interceptor Injector that inherits from IInjector that is named in the pattern ErrorUnit.Injector_<Name of IOC Library> for example https://www.nuget.org/packages/ErrorUnit.Injector_SimpleInjector or if you do not want to be limited to what your IOC library sees, or don't use an IoC library consider using https://www.nuget.org/packages/ErrorUnit.Injector_PostSharp (no other interception methods needed).

Another key feature is the ability to serialize Entity Framework DbContext classes; read up on the DbContextSerializer to learn how to set your DbContext class up.

Finally the last thing you should set up is a ILogger library; for example https://www.nuget.org/packages/ErrorUnit.Logger_Elmah .

The ErrorUnit.Attributes namespace contains classes for attaching filter attributes to MVC and Web API; recording the call to the respective controller in case of an error.

The ErrorUnit.Interfaces namespace contains classes for extending ErrorUnit; allowing developers to integrate their own logger or IoC interception and make them compatible with ErrorUnit.

The ErrorUnit.JsonSerializer namespace contains classes that ErrorUnit uses for JSON serialization.

The ErrorUnit.Models namespace contains classes that ErrorUnit uses.