Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/csharp/327.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181

Warning: file_get_contents(/data/phpspider/zhask/data//catemap/0/asp.net-core/3.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181

Warning: file_get_contents(/data/phpspider/zhask/data//catemap/5/date/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
C# 如何配置多个异常处理程序_C#_Asp.net Core_Asp.net Core Middleware - Fatal编程技术网

C# 如何配置多个异常处理程序

C# 如何配置多个异常处理程序,c#,asp.net-core,asp.net-core-middleware,C#,Asp.net Core,Asp.net Core Middleware,我正在尝试配置中间件管道,以使用两个不同的异常处理程序来处理同一个异常。例如,我尝试使用自定义处理程序和内置developerCeptionPageMiddleware,如下所示: public void Configure(IApplicationBuilder app, IHostingEnvironment env) { if (env.IsDevelopment()) { app.UseDeveloperExceptionPage();

我正在尝试配置中间件管道,以使用两个不同的异常处理程序来处理同一个异常。例如,我尝试使用自定义处理程序和内置developerCeptionPageMiddleware,如下所示:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();                
        app.ConfigureCustomExceptionHandler();
    }
    else
    {
        app.UseExceptionHandler("/Home/Error");                               
        app.ConfigureCustomExceptionHandler();            
        app.UseHsts();
    }

    app.UseHttpsRedirection();
    app.UseStaticFiles();
    app.UseCookiePolicy();
    app.UseAuthentication();
    app.UseMvcWithDefaultRoute();
}
我的目标是让自定义处理程序完成自己的事情(日志记录、遥测等),然后将(next())传递给另一个显示页面的内置处理程序。我的自定义处理程序如下所示:

public static class ExceptionMiddlewareExtensions
{
    public static void ConfigureCustomExceptionHandler(this IApplicationBuilder app)
    {            
        app.UseExceptionHandler(appError =>
        {
            appError.Use(async (context, next) =>
            {                    
                var contextFeature = context.Features.Get<IExceptionHandlerFeature>();
                if (contextFeature != null)
                {
                    //log error / do custom stuff

                    await next();
                }
            });
        });
    }
}
公共静态类例外middlewareextensions
{
公共静态无效配置CustomExceptionHandler(此IAApplicationBuilder应用程序)
{            
app.UseExceptionHandler(appError=>
{
appError.Use(异步(上下文,下一步)=>
{                    
var contextFeature=context.Features.Get();
if(contextFeature!=null)
{
//日志错误/执行自定义操作
等待下一个();
}
});
});
}
}
我无法让CustomExceptionHandler将处理传递到下一个中间件。我将看到以下页面:

404错误:

我试着切换顺序,但是开发人员异常页面接管了,并且没有调用自定义异常处理程序

我想做的一切可能吗

更新:

解决方案是采纳Simonare最初的建议,在
Invoke
方法中重新抛出异常。我还必须通过替换
handleExceptionSync
方法中的以下内容来消除任何类型的响应干扰:

context.Response.ContentType=“application/json”;
context.Response.StatusCode=(int)代码;
返回context.Response.WriteAsync(结果)

与:

returntask.CompletedTask


<>而不是调用两个不同的异常处理中间件,您可以考虑在<代码> home /错误< /代码>

中添加日志记录。
[AllowAnonymous]
public IActionResult Error()
{
    //log your error here
    return View(new ErrorViewModel 
        { RequestId = Activity.Current?.Id ?? HttpContext.TraceIdentifier });
}
或者,您可以使用自定义的Expection处理中间件

public class ErrorHandlingMiddleware
{
    private readonly RequestDelegate _next;

    public ErrorHandlingMiddleware(RequestDelegate next)
    {
        _next = next;
    }

    public async Task Invoke(HttpContext context, IHostingEnvironment env)
    {
        try
        {
            await _next(context);
        }
        catch (Exception ex)
        {
            if (!context.Response.HasStarted)
                await HandleExceptionAsync(context, ex, env);
            throw;
        }
    }

    private Task HandleExceptionAsync(HttpContext context, Exception exception, IHostingEnvironment env)
    {
        var code = HttpStatusCode.InternalServerError; // 500 if unexpected
        var message = exception.Message;

        switch (exception)
        {
            case NotImplementedException _:
                code = HttpStatusCode.NotImplemented; 
                break;
            //other custom exception types can be used here
            case CustomApplicationException cae: //example
                code = HttpStatusCode.BadRequest;
                break;
        }

        Log.Write(code == HttpStatusCode.InternalServerError ? LogEventLevel.Error : LogEventLevel.Warning, exception, "Exception Occured. HttpStatusCode={0}", code);


        context.Response.ContentType = "application/json";
        context.Response.StatusCode = (int)code;
        return Task.Completed;
    }
}
只需在IAApplicationBuilder方法中注册它

  public void Configure(IApplicationBuilder app)
  {
        app.UseMiddleware<ErrorHandlingMiddleware>();
  }
public void配置(IApplicationBuilder应用程序)
{
app.UseMiddleware();
}

谢谢您的回复。您的建议是始终使用单个异常处理程序,但我希望保留默认的开发人员异常页面,同时利用中间件管道进行自定义日志记录。
ErrorHandlingMiddleware
将适合您。您可以拥有尽可能多的中间件处理程序(当然,请记住它们具有性能影响)您是否可以更新您的答案,以包括如何将
ErrorHandlingMiddleware
与内置的
app.UseDeveloperExceptionPage()
app.UseExceptionHandler(“/Home/Error”)并排注册
中间件?我已经尝试过实现这个类,但它仍然完全接管了其他内置中间件。嗨,Simonare,谢谢!一旦我了解了中间件类是如何工作的,我就设法通过一个小小的调整让它工作起来。要将异常传递到管道中的下一个中间件,只需在Invoke方法中重新显示异常。Simonare,请在调用的catch块末尾添加“throw;”,并返回
Task.Completed
,而不是
context.Response.WriteAsync(result)),以更新您的答案