当前位置：文江博客话题详情

如何覆盖 ASP.NET 中的页面加载生命周期以防止加载 ASPX 表单？

发布于 2024-07-17 08:02:41 字数 212 浏览 7 评论 0原文

我需要在多个 ASPX 代码隐藏文件中测试某个条件，并且在某些情况下，希望完全绕过正常的页面加载过程，以便不加载相应的 ASPX 页面。相反，我想向浏览器发送通过代码隐藏方法编写的自定义响应。

有谁知道从哪里开始 - 页面生命周期中要覆盖哪些方法以及确保在正常 ASPX 页面内容被抑制时将我的自定义 Response.Write 发送到浏览器的最佳技术？

谢谢。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

一绘本一梦想 2024-07-24 08:02:41

可能是最简单的方法 - 使用 Page_Load()。

protected void Page_Load(object sender, EventArgs e)
{
    bool customResponse = true;
    if (customResponse)
    {
        Response.Write("I am sending a custom response");
        Response.End(); //this is what keeps it from continuing on...
    }
}

Probably the easiest way to do it - use Page_Load().

protected void Page_Load(object sender, EventArgs e)
{
    bool customResponse = true;
    if (customResponse)
    {
        Response.Write("I am sending a custom response");
        Response.End(); //this is what keeps it from continuing on...
    }
}

回复收藏 0 原文

瘫痪情歌 2024-07-24 08:02:41

使用 Response.End() 的“简单”方法对性能来说很糟糕，会抛出终止线程的异常。

http://blogs.msdn.com/b/tmarq/archive/2009/06/25/ Correct-use-of-system-web-httpresponse-redirect.aspx

http://weblogs.asp.net/hajan/archive/2010/09/26/why-not-to-use-httpresponse-close-and-httpresponse-end.aspx

我有同样的问题并以这种方式解决了。这是一个两步过程：首先调用 HttpApplication.CompleteRequest() 并退出处理。接下来重写 Render() 以便不调用基本方法。示例代码则变为：

bool customResponse = true;

protected void Page_Load(object sender, EventArgs e)
{
    if (customResponse)
    {
        Response.Write("I am sending a custom response");
        this.Context.ApplicationInstance.CompleteRequest();
        return;   // Bypass normal processing.
    }
    // Normal processing...
}

protected override void Render(HtmlTextWriter writer)
{
    if (!customResponse)
        base.Render(writer);        // Then write the page as usual.
}

The "easy" way to do it, with Response.End() is terrible for performance, throwing an exception which terminates the thread.

http://blogs.msdn.com/b/tmarq/archive/2009/06/25/correct-use-of-system-web-httpresponse-redirect.aspx

http://weblogs.asp.net/hajan/archive/2010/09/26/why-not-to-use-httpresponse-close-and-httpresponse-end.aspx

I had the same question and solved it this way. It's a two-step process: First call HttpApplication.CompleteRequest() and exit your processing. Next override Render() so that the base method is not called. The example code then becomes:

bool customResponse = true;

protected void Page_Load(object sender, EventArgs e)
{
    if (customResponse)
    {
        Response.Write("I am sending a custom response");
        this.Context.ApplicationInstance.CompleteRequest();
        return;   // Bypass normal processing.
    }
    // Normal processing...
}

protected override void Render(HtmlTextWriter writer)
{
    if (!customResponse)
        base.Render(writer);        // Then write the page as usual.
}

回复收藏 0 原文