Net6.0 MVC中View.RenderAsync()引发Cannot access a closed Stream异常求助

问题根源 #

1. 同步阻塞调用异步的RenderAsync方法（GetAwaiter().GetResult()）会导致请求上下文混乱，触发响应流的提前释放。
2. 直接复用原控制器的ControllerContext创建ViewContext，视图渲染过程中会意外操作原请求的Response流，导致后续JSON写入时流已被关闭。

修复方案 #

1. 改为异步的局部视图转字符串方法 #

创建独立的请求上下文副本，避免视图渲染影响原响应流，同时使用异步调用避免阻塞问题：

using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.ViewEngines;
using Microsoft.AspNetCore.Mvc.ViewFeatures;
using System.IO;
using System.Threading.Tasks;

public static async Task<string> RenderPartialViewToStringAsync(Controller controller, string partialPath, object model)
{
    if (string.IsNullOrEmpty(partialPath))
    {
        partialPath = controller.GetActionNameFromRouteData();
    }

    // 复制ViewData和TempData，隔离视图渲染上下文
    var viewData = new ViewDataDictionary(controller.ViewData)
    {
        Model = model
    };
    var tempData = controller.TempData;

    using var stringWriter = new StringWriter();
    
    var viewEngine = DependencyResolverHelper.GetService<ICompositeViewEngine>();
    var viewResult = viewEngine.FindView(controller.ControllerContext, partialPath, false);

    if (viewResult.View == null)
    {
        throw new InvalidOperationException($"无法找到局部视图: {partialPath}");
    }

    // 创建独立的HttpContext和ControllerContext，避免触碰原响应流
    var tempHttpContext = new DefaultHttpContext(controller.HttpContext.RequestServices)
    {
        Request = { Path = controller.HttpContext.Request.Path }
    };
    var tempControllerContext = new ControllerContext(new ActionContext(tempHttpContext, controller.ControllerContext.RouteData, controller.ControllerContext.ActionDescriptor))
    {
        ViewData = viewData,
        TempData = tempData
    };

    var viewContext = new ViewContext(
        tempControllerContext,
        viewResult.View,
        viewData,
        tempData,
        stringWriter,
        new HtmlHelperOptions()
    );

    await viewResult.View.RenderAsync(viewContext);

    return stringWriter.ToString();
}

2. 异步调用该方法并返回JSON #

在控制器Action中使用异步调用，确保整个请求流程是异步的：

public async Task<IActionResult> AjaxLoadPartial()
{
    var viewModel = new YourViewModel();
    // 替换为你的局部视图路径
    var renderedHtml = await RenderPartialViewToStringAsync(this, "~/Views/Shared/YourPartialView.cshtml", viewModel);
    
    // 如果使用自定义JsonNetResult，确保它是异步实现的
    return new JsonNetResult
    {
        Data = new { Html = renderedHtml },
        SerializerSettings = new Newtonsoft.Json.JsonSerializerSettings { Formatting = Newtonsoft.Json.Formatting.Indented }
    };
}

3. 确保自定义JsonNetResult支持异步 #

如果使用自定义的JSON结果类，必须实现异步的ExecuteResultAsync方法，避免同步操作导致的流问题：

using Microsoft.AspNetCore.Mvc;
using Newtonsoft.Json;
using System.Threading.Tasks;

public class JsonNetResult : IActionResult
{
    public object Data { get; set; }
    public JsonSerializerSettings SerializerSettings { get; set; } = new JsonSerializerSettings();

    public async Task ExecuteResultAsync(ActionContext context)
    {
        if (context == null)
            throw new System.ArgumentNullException(nameof(context));

        var response = context.HttpContext.Response;
        response.ContentType = string.IsNullOrEmpty(response.ContentType) ? "application/json" : response.ContentType;

        if (Data != null)
        {
            var json = JsonConvert.SerializeObject(Data, SerializerSettings);
            await response.WriteAsync(json, context.HttpContext.RequestAborted);
        }
    }
}

关键说明 #

• 异步优先：ASP.NET Core 设计为异步优先，同步阻塞异步方法会引发上下文死锁、资源释放异常等问题，必须全程使用异步流程。
• 上下文隔离：通过创建独立的HttpContext和ControllerContext，彻底避免视图渲染过程中修改原请求的响应流，从根源上解决ObjectDisposedException。
• 数据隔离：复制ViewData和TempData，确保视图渲染使用独立的数据上下文，不会影响原控制器的状态。

内容的提问来源于stack exchange，提问作者Uladzislau Kurbatski