包：Autofac.Extensions.DependencyInjection（6.0.0），Autofac.extras.DynamicProxy（4.5.0）
通过遵循ASP.NET Core 4.0和Interceptor文档，我试图为我们的应用程序中服务Web API控制器的所有服务类/接口设计一个拦截器的原型。拦截器只是使用Serlog的简单Log操作：
public MethodCallInterceptor()
{
}
public void Intercept(IInvocation invocation)
{
var text = invocation.Method.Name;
Log.Logger.Debug($"Interceptor (Method): {text}");
invocation.Proceed();
}
我们的主应用程序使用ComApiApplication将Autofac设置为“启动”类：
public static void Main(string[] args)
{
CreateHostBuilder(args).Build().Run();
}
public static IHostBuilder CreateHostBuilder(string[] args)
{
return Host.CreateDefaultBuilder(args)
.UseServiceProviderFactory(new AutofacServiceProviderFactory())
.ConfigureWebHostDefaults(webBuilder => webBuilder.UseStartup<ComsApiApplication>());
}
在ComsApiApplication中，我在ConfigureServices中注册了大多数ASP.NET MVC服务（例如，身份验证，授权等）。然后，我在其ConfigureContainer函数中的几个服务程序集中连接了类的Interceptor：
public void ConfigureContainer(ContainerBuilder builder)
{
foreach (var assembly in Options.Assemblies)
{
// Add application services: IService => Service.
var registrations = assembly.GetExportedTypes()
.Where(type => type.Namespace != null && type.Namespace.Contains(".Services") && type.GetInterfaces().Any() && !type.IsAbstract)
.Select(type => new
{
Service = type.GetInterfaces().Single(inf => inf.Name.Contains(type.Name)),
Implementation = type
});
foreach (var registration in registrations)
{
//builder.RegisterType(registration.Implementation).As(registration.Service).InstancePerDependency().EnableInterfaceInterceptors().InterceptedBy(typeof(MethodCallInterceptor));
builder.RegisterType(registration.Implementation).As(registration.Service).EnableInterfaceInterceptors().InstancePerDependency().InterceptedBy(typeof(MethodCallInterceptor));
}
builder.Register(c => new MethodCallInterceptor());
}
}
但是，当我运行带有导致调用那些服务中的接口函数的请求的应用程序时（在我们的接口和服务类中存在继承关系，我会收到以下异常，感谢您对确定问题的任何帮助：
Autofac.Core.DependencyResolutionException：执行解析操作时引发了异常。有关详细信息，请参见InnerException。---> Castle.DynamicProxy.ProxyGenerationException：这是DynamicProxy2错误：代理的目标类型实现Castle.DynamicProxy.IProxyTargetAccessor，它是DynamicProxy基础结构接口，您永远不要自己实现它。您是否要代理现有的代理？在Castle.DynamicProxy.Generators.BaseProxyGenerator.HandleExplicitlyPassedProxyTargetAccessor（ICollection1 targetInterfaces, ICollection1另外的接口）处在Castle.DynamicProxy.Generators.InterfaceProxyWithTargetGenerator.GetTypeImplementerMapping（Type []接口，类型proxyTargetType，IEnumerable1& contributors, INamingScope namingScope)
at Castle.DynamicProxy.Generators.InterfaceProxyWithTargetGenerator.GenerateType(String typeName, Type proxyTargetType, Type[] interfaces, INamingScope namingScope)
at Castle.DynamicProxy.Generators.InterfaceProxyWithTargetGenerator.<>c__DisplayClass6_0.<GenerateCode>b__0(String n, INamingScope s)
at Castle.DynamicProxy.Generators.BaseProxyGenerator.ObtainProxyType(CacheKey cacheKey, Func3工厂）在Castle.DynamicProxy.Generators.InterfaceProxyWithTargetGenerator.GenerateCode（类型proxyTargetType，类型[]接口，ProxyGenerationOptions选项）处在Castle.DynamicProxy.DefaultProxyBuilder.CreateInterfaceProxyTypeWithTarget（Type interfaceToProxy，Type [] AdditionalInterfacesToProxy，typetargetType，ProxyGenerationOptions选项）在Castle.DynamicProxy.ProxyGenerator.CreateInterfaceProxyTypeWithTarget（Type interfaceToProxy，Type [] AdditionalInterfacesToProxy，type targetType，ProxyGenerationOptions选项）at Castle.DynamicProxy.ProxyGenerator.CreateInterfaceProxyWithTarget（Type interfaceToProxy，Type [] AdditionalInterfacesToProxy，对象目标，ProxyGenerationOptions选项，IInterceptor []拦截器）在Castle.DynamicProxy.ProxyGenerator.CreateInterfaceProxyWithTarget（Type interfaceToProxy，Type [] AdditionalInterfacesToProxy，Object target，IInterceptor []拦截器）在Autofac.Extras.DynamicProxy.RegistrationExtensions。<> c__DisplayClass9_03.<EnableInterfaceInterceptors>b__0(Object sender, ActivatingEventArgs1 e）在Autofac.Core.Registration.ComponentRegistration.RaiseActivating（IComponentContext上下文，IEnumerable1 parameters, Object& instance)
at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable1参数，Object＆decoratorTarget）在Autofac.Core.Resolving.InstanceLookup.Execute（）在Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance（ISharingLifetimeScope currentOperationScope，ResolveRequest请求）在Autofac.Core.Resolving.ResolveOperation.ResolveComponent（ResolveRequest请求）在Autofac.Core.Resolving.ResolveOperation.Execute（ResolveRequest请求）---内部异常堆栈跟踪的结尾---在Autofac.Core.Resolving.ResolveOperation.Execute（ResolveRequest请求）在Autofac.Core.Lifetime.LifetimeScope.ResolveComponent（ResolveRequest请求）在Autofac.ResolutionExtensions.TryResolveService（IComponentContext上下文，服务服务，IEnumerable1 parameters, Object& instance)
at Autofac.ResolutionExtensions.ResolveOptionalService(IComponentContext context, Service service, IEnumerable1参数）在Autofac.ResolutionExtensions.ResolveOptional（IComponentContext上下文，类型serviceType，IEnumerable`1参数）在Autofac.ResolutionExtensions.ResolveOptional（IComponentContext上下文，类型serviceType）在Autofac.Extensions.DependencyInjection.AutofacServiceProvider.GetService（Type serviceType）在Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService（IServiceProvider sp，Type type，Type requiredBy，Boolean isDefaultParameterRequired）在lambda_method（Closure，IServiceProvider，Object []）在Microsoft.AspNetCore.Mvc.Controllers.ControllerActivatorProvider。<> c__DisplayClass4_0.b__0（ControllerContext controllerContext）在Microsoft.AspNetCore.Mvc.Controllers.ControllerFactoryProvider。<> c__DisplayClass5_0.g__CreateController | 0（ControllerContext controllerContext）处。在Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next（状态和下一个，范围和范围，对象和状态，布尔值和isCompleted）处在Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync（）---从之前引发异常的位置开始的堆栈结束跟踪---在Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited | 25_0（ResourceInvoker调用程序，Task lastTask，Next状态，Scope作用域，对象状态，布尔值isCompleted）Microsoft.AspNetCore.Mvc.Infrastructure.SystemTextJsonResultExecutor：信息：正在执行JsonResult，写入类型为'System.String'的值。
以下内容来自Google翻译：碰巧的是，我只是解决了这个问题，但这不是正确的解决方案。只需将Autofac.Extensions.DependencyInjection包降级为5.0.1
即可解决问题。