Home/ Questions/Q 6644817
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T00:12:41+00:00

I’m trying to fire off several HTTP requests from an ASP.NET page. The page

  • 0

I’m trying to fire off several HTTP requests from an ASP.NET page. The page itself doesn’t need to know the response and should continue processing & deliver the page regardless.

I’ve tried putting the HTTP code in a BackgroundWorker and running it asynchronously, however I initially got the following error;

Asynchronous operations are not allowed in this context. Page starting
an asynchronous operation has to have the Async attribute set to true
and an asynchronous operation can only be started on a page prior to
PreRenderComplete event.

So I did as I was told and gave the page the Async attribute. I then did some research and discovered that my BackgroundWorker isn’t actually performing an asynchronous operation as I expected. Some background reading (http://www.pluralsight-training.net/community/blogs/mike/archive/2005/11/04/16213.aspx) informed me that;

PreRender and PreRenderComplete events [do] not resume until all of
the timeout event handlers for all of the registered async tasks have
been invoked and return.

How do I ensure that my BackgroundWorker does not suspend the processing of the page?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Another option to look at is ThreadPool.QueueUserWorkitem(). It will fire something off asynchronously. It will also use on of the threads in the asp.net threadpool.

    I’ve typically used threadPool on the server and BackGroundWorker in gui/winforms. That’s not to say it can’t be done.

    That’s at least something else to try if you get stuck with BackgroundWorker…

    Here’s a few other SO posts:

    ThreadPool.QueueUserWorkItem uses ASP.Net

    ThreadPool.QueueUserWorkItem with a lambda expression and anonymous method

    ThreadPool.QueueUserWorkItem with function argument

    • 0