0

What I have in mind is some sort of logging mechanism. Most of my classes get an ILogger service by dependency injection. What I'd like is to have some sort of "path" information automatically attached to the logging service. By "path" i mean something like "where was the Log()-calling instance injected", all the way up to the top-most scope.

Example:

class A
{
    public A(string name, B b, ILogger logger)
    {
        ...
    }
}

class B
{
    public B(string name, C c, ILogger logger)
    {
        ...
    }
}

class C
{
    public C(string name, ILogger logger)
    {
        logger.Log("Hello World");
    }
}

Then, when C is created, I want to get this output:

A[nameOfA] -> B[nameOfB] -> C[nameOfC]: Hello World

Any ideas how to achieve this in a generic way, i.e. without manual wiring each class? I already tried to access this information via ParentContext and ParentRequest inside the .ToMethod(..) binding, but didn't come up with a solution.

Best regards Kc

Kc_
  • 201
  • 4
  • 11
  • "Most of my classes get an ILogger service by dependency injection.". That reminds me of this old [q/a](https://stackoverflow.com/a/9915056/264697), and [this blogpost](https://blog.codinghorror.com/the-problem-with-logging/) from Jeff Atwood. – Steven Aug 08 '18 at 18:02
  • That said, you'll find the answer to your question [in the Ninject documentation](https://github.com/ninject/Ninject/wiki/Contextual-Binding#using-the-request-context-in-a-factory-or-factory-method-to-do-contextual-binding). – Steven Aug 08 '18 at 18:04

0 Answers0