Dependency Injection wiring lost

Hi,

Thanks for the great library!

I have run into an issue where variables are lost that are setup in the constructor via the DI framework. I use StructureMap to wire the class up, this wiring instantiates a field that I need to reference in a method that I am applying advice to. The issue is only prevalent when I place the attribute at the top of the class, when I place the attribute on top of the method in question, all works _fine!

This is the relevant code:

RepositoryClass:

[RepositoryExceptionAdvice] _<-- _settings is null if attribute is placed here_
public class ExampleRepository : IExampleRepository
{
  private readonly ISettings _settings;

  public ComponentTermsRepository(ISettings settings)
  {
    _settings = settings;
  }

  //Advice
  _<-- _settings is fine if attribute is placed here_
  public async Task<List<Example>> List(Guid? ExampleId)
  {
    var test = _settings.TenantId _<- Settings here is null_
  }
}

**Advice Class**
    public class RepositoryExceptionAdvice : Attribute, IMethodAsyncAdvice
    {
        public async Task Advise(MethodAsyncAdviceContext context)
        {
            try
            {
                if (context.IsTargetMethodAsync)
                {
                    await context.ProceedAsync();
                }
            }
            catch (DatabaseException e)
            {
            }
         }
      }

[BOENDAGGER]

Eish, just got your second response, so you can ignore the above comment.

Yes, that was a bit stupid of me blush

What would the recommended way be to ignore the advice for the constructor? Would this be the best approach:

if (!context.TargetMethod.IsConstructor) [proceed]

[picrap]

The idea is that a IMethodAsyncAdvice works fine with both sync and async methods.