Home/ Questions/Q 776897
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T19:31:26+00:00

I have an ASP.NET 2.0 page with many repeating blocks, including a third-party server-side

  • 0

I have an ASP.NET 2.0 page with many repeating blocks, including a third-party server-side control (so it’s not just plain HTML). Each is quite expensive to generate, in terms of both CPU and RAM. I’m currently using a standard Repeater control for this.

There are two problems with this simple approach:

  1. The entire page must be rendered before any of it is returned to the client, so the user must wait a long time before they see any data. (I write progress messages using Response.Write, so there is feedback, but no actual results.)
  2. The ASP.NET worker process must hold everything in memory at the same time. There is no inherent needs for this: once one block is processed it won’t be changed, so it could be returned to the client and the memory could be freed.

I would like to somehow return these blocks to the client one at a time, as each is generated. I’m thinking of extracting the stuff inside the Repeater into a separate page and getting it repeatedly using AJAX, but there are some complications involved in that and I wonder if there is some simper approach. Ideally I’d like to keep it as one page (from the client’s point of view), but return it incrementally.

Another way would be to do something similar, but on the server: still create a separate page, but have the server access it and then Response.Write() the HTML it gets to the response stream for the real client request. Is there a way to avoid an HTTP request here, though? Is there some ASP.NET method that would render a UserControl or a Page outside of an HTTP request and simply return the HTML to me as a string?

I’m open to other ideas on how to do this as well.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Another way would be to do something similar, but on the server: still create a separate page, but have the server access it and then Response.Write() the HTML it gets to the response stream for the real client request.

    You could do this if you extract the contents of each repeater row into a UserControl. You could then load the control dynamically (if need be) using LoadControl method, give it the proper data it should render (call DataBind if necessary) then render it to the response stream using the Render method. This is basically what you had in mind without the mess of creating a whole new request.

    Disclaimer: I don’t know if this will perform better or worse than your current solution in terms of total execution time.

    • 0