Autofac.依赖项解析异常：在类型“xxxController”上使用“DefaultConstructorFinder”找到的任何构造函数都不能使用可用的服务和参数调用：

开发工具：vs2022企业版

框架：abp vnext 3.1

操作系统：windows11

异常信息：

[15:03:03 ERR] Connection id "0HMVNSKI9MNE9", Request id "0HMVNSKI9MNE9:00000005": An unhandled exception was thrown by the application.
Autofac.Core.DependencyResolutionException: An exception was thrown while activating Imagine.Mes.MesOrder.HttpApi.Controllers.WorkTaskReportController.
 ---> Autofac.Core.DependencyResolutionException: None of the constructors found with 'Autofac.Core.Activators.Reflection.DefaultConstructorFinder' on type 'Imagine.Mes.MesOrder.HttpApi.Controllers.WorkTaskReportController' can be invoked with the available services and parameters:
Cannot resolve parameter 'Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.ReportChangeRecord,System.Guid] reportChangeRecordRepository' of constructor 'Void .ctor(Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.WorkTaskReport,System.Int32], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.WorkOrder,System.Guid], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.WorkTask,System.Int32], Imagine.Mes.Base.ServiceDb.IDMesBaseService, Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.Unit,System.Int32], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.FactoryModel,System.Guid], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.Product,System.String], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.RouteOrder,System.String], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.RouteStep,System.String], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.WorkClass,System.Int32], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.WorkGroup,System.Int32], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.AbpUsers,System.Guid], Imagine.Mes.MesOrder.Application.Services.IWorkTaskReportService, Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.WorkTaskReportUser,System.Guid], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.Supplier,System.String], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.ReportRouteOperationSmall,System.Guid], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.ReportChangeRecord,System.Guid], Microsoft.Extensions.Logging.ILogger`1[Imagine.Mes.MesOrder.HttpApi.Controllers.WorkTaskReportController], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesBase.Domain.Entities.RouteOperation,System.String], Volo.Abp.Domain.Repositories.IRepository`2[Imagine.Mes.MesOrder.Domain.Entities.WarehousingApplication,System.Guid])'.
   at Autofac.Core.Activators.Reflection.ReflectionActivator.GetValidConstructorBindings(ConstructorInfo[] availableConstructors, IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Resolving.InstanceLookup.CreateInstance(IEnumerable`1 parameters)
   --- End of inner exception stack trace ---
   at Autofac.Core.Resolving.InstanceLookup.CreateInstance(IEnumerable`1 parameters)
   at Autofac.Core.Resolving.InstanceLookup.Execute()
   at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, ResolveRequest request)
   at Autofac.Core.Resolving.ResolveOperation.Execute(ResolveRequest request)
   at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
   at Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable`1 parameters)
   at Microsoft.AspNetCore.Mvc.Controllers.ServiceBasedControllerActivator.Create(ControllerContext actionContext)
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerFactoryProvider.<>c__DisplayClass5_0.<CreateControllerFactory>g__CreateController|0(ControllerContext controllerContext)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ExceptionContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeNextResourceFilter()

本来程序好好地，突然测试跟我说某个页面报错了，很诧异，调试了下，发现真的不行了，接口方法的断点都命中不了，看异常提示，是某个实体的构造函数有问题，检查了一遍也没问题，只要报报异常的实体的依赖注入注释掉这个页面的接口就可以正常访问了，但这个依赖注入又不能注释掉，因为有用到。

检查一下最近谁提交了代码，最终发现有人把代码覆盖了，EFCore项目中MesOrderDbContext.cs文件里的DbSet<xxx>被删掉了，加上就行了。