SaasKit.Multitenancy 与 Asp Net Core 2.2 不兼容？

Question

我创建了一个 .NET Core API 控制器，并且在 POST 方法中，我尝试使用 CreatedAtActionResult 方法将路由作为 Location Header 包含在我的响应中。

[ApiController, Route("v1/[controller]")]
public class WidgetController: ControllerBase
{
    public WidgetController(IWidgetService service)
    {
        _service = service;
    }

    private readonly IWidgetService _service;

    [HttpGet("{id}", Name = "GetSingle")]
    public IActionResult GetSingle(Guid id)
    {
        var result = _service.Get(id);

        return Ok(result);
    }

    [HttpPost]
    public IActionResult Post(WidgetModel model)
    {
        var result = _service.Post(model);

        return result == Guid.Empty
                    ? (IActionResult) BadRequest("No changes saved.")
                    : CreatedAtAction(nameof(GetSingle),
                                      new {id = result},
                                      model);
    }
}

当我启动应用程序时，POSTman 对 POST 的第一次调用运行没有问题。对象和位置标头 URL 都按预期生成。但是，如果我在代码仍在运行时再次尝试访问该端点，则会收到以下错误：

System.InvalidOperationException：没有服务类型为“Microsoft.AspNetCore.Routing.IEndpointAddressScheme1[Microsoft.AspNetCore.Routing.RouteValuesAddress]' has been registered. at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType) at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider) at Microsoft.AspNetCore.Routing.DefaultLinkGenerator.GetEndpoints[TAddress](TAddress address) at Microsoft.AspNetCore.Routing.DefaultLinkGenerator.GetPathByAddress[TAddress](HttpContext httpContext, TAddress address, RouteValueDictionary values, RouteValueDictionary ambientValues, Nullable1 pathBase、FragmentString 片段、LinkOptions 选项） 在 Microsoft.AspNetCore.Routing.LinkGeneratorRouteValuesAddressExtensions.GetPathByRouteValues（LinkGenerator 生成器，HttpContext httpContext，字符串 routeName，对象值，Nullable1 pathBase, FragmentString fragment, LinkOptions options) at Microsoft.AspNetCore.Mvc.Routing.EndpointRoutingUrlHelper.Action(UrlActionContext urlActionContext) at Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Action(IUrlHelper helper, String action, String controller, Object values, String protocol, String host, String fragment) at Microsoft.AspNetCore.Mvc.UrlHelperExtensions.Action(IUrlHelper helper, String action, String controller, Object values, String protocol, String host) at Microsoft.AspNetCore.Mvc.CreatedAtActionResult.OnFormatting(ActionContext context) at Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.ExecuteAsync(ActionContext context, ObjectResult result) at Microsoft.AspNetCore.Mvc.ObjectResult.ExecuteResultAsync(ActionContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeResultAsync(IActionResult result) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResultFilterAsync[TFilter,TFilterAsync]() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResultExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeResultFilters() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext) at SaasKit.Multitenancy.Internal.TenantResolutionMiddleware1.Invoke（HttpContext 上下文，ITenantResolver`1 tenantResolver） 在 Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext 上下文)

我已经尝试将CreatedAtAction 替换为Ok，并且在我单击POSTman 中的按钮时，200 结果将返回。

Post 方法中的代码成功处理，它将移至我创建的过滤器的OnActionExecuted 方法。我试过查看ActionExecutedContext 对象的所有属性，但没有发现任何异常。一旦我退出那个空的OnActionExecuted 方法，调用就会返回 500 状态代码和错误页面内的上述堆栈跟踪。我确实有一个异常过滤器，但它没有被触及。

以前有人遇到过这个问题吗？

作为参考，这是我的启动配置：

public IServiceProvider ConfigureServices(IServiceCollection services)
{
    services.AddMultitenancy<AppTenant, CachingAppTenantResolver>();

    services.AddAutoMapper()
            .AddSingleton(ConfigureAutoMapper())
            .AddMvc(options =>
            {
                options.Filters.Add<ValidatorActionFilter>();
                options.Filters.Add<ErrorHandlingFilter>();
            })
            .AddFluentValidation(validation => {
                validation.RunDefaultMvcValidationAfterFluentValidationExecutes = false;
                validation.ImplicitlyValidateChildProperties = true;
                validation.RegisterValidatorsFromAssemblyContaining<WidgetModelValidator>();
                })
            .SetCompatibilityVersion(CompatibilityVersion.Version_2_2)
            .ConfigureApiBehaviorOptions(options =>
            {
                options.SuppressModelStateInvalidFilter = true;
                options.SuppressMapClientErrors = true;
            });

    services.AddEntityFrameworkSqlServer()
            .AddDbContext<MyContext>();

    services.Configure<MultitenancyOptions>(configuration.GetSection("Multitenancy"));

    services.AddCors(options =>
    {
        options.AddDefaultPolicy(
            builder =>
            {
                builder.WithOrigins("http://localhost:4200").AllowAnyHeader().AllowAnyMethod();
            });
    });

    ConfigureContainer(container);

    return provider;
}

Answer 1

尝试设置CompatibilityVersion.Version_2_0 或2.1 而不是2.2？

EndpointRouting 在 2.2 的覆盖下是一个相当大的变化，您的 3rd 方插件可能不兼容。

将兼容性设置回 2.1 通常不需要在控制器中更改任何代码，因此成本相当低。