Click here to Skip to main content
15,040,003 members
Articles / Web Development / HTML
Posted 11 Jul 2005


79 bookmarked

Use the Asynchronous Power of ASP.NET to Create a Simple, Reusable Page for Displaying a Processing Message

Rate me:
Please Sign up or sign in to vote.
3.42/5 (24 votes)
11 Jul 20053 min read
Use the asynchronous capabilaties of ASP.NET to inform your users when a long process is happening.

Sample Image - ProcessingMessage.gif


Sometimes we may find it necessary for our users to run long processes when using the web as a user interface. Since patience is not a typical trait of web users, we run into the issue of needing to entertain them, prevent multiple clicks, or keep them from pulling their hair out while we're running time-consuming processes in the background. There are several tactics for doing this on the web, but I have found none of these to be as simple as employing .NET's asynchronous threading. I hope that you find this helpful.

Using the code

The relevant portion of the sample application included with this article consists of two C# Web Forms i.e., SubmitLongProcess.aspx, ProcessingMessage.aspx. SubmitLongProcess.aspx is used for starting the process and redirecting the user to ProcessingMessage.aspx. ProcessingMessage.aspx is the processing message page that is used to display a friendly message to the user while the long process is running in the background. Once the long process completes, ProcessingMessage.aspx redirects the user to a specified page.


As you can see in the code below, .NET makes firing off a new thread quite simple. Without fully qualifying the code, you'll need to include a using directive to the System.Web.Threading namespace.

using System.Web.Threading

You can see that all I'm doing in the SubmitButton_Click event is initializing the session variable, initializing and starting the new thread, then redirecting the user to the ProcessingMessage.aspx page. Notice that I've included two querystring name/value pairs in the URL parameter of the Response.Redirect method. One is used to specify the redirect page after processing is complete and the other is used to inform ProcessingMessage.aspx what session variable to check.

Response.Redirect("ProcessingMessage.aspx?redirectPage" + 
      "=SubmitLongProcess.aspx&ProcessSessionName=" + PROCESS_NAME);

The StartLongProcess() method runs in the background on a new thread while the user is redirected to the ProcessingMessage.aspx page. This method consists of two important lines of code. The first is used to mimic a long process by forcing the thread to sleep for a specified amount of time. Once the thread is done sleeping, the second line of code is used to set the session variable equal to true. Setting this variable equal to true informs the ProcessingMessage.aspx that the long process is complete.

using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Threading;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;

namespace AsynchronousProcessing
    public class ProcessingMessage : System.Web.UI.Page
        protected System.Web.UI.WebControls.TextBox txtProcessLength;
        protected System.Web.UI.WebControls.Button SubmitButton;
        private const string PROCESS_NAME = "Process";

        private void Page_Load(object sender, System.EventArgs e)


        private void SubmitButton_Click(object sender, System.EventArgs e)
            //Initialize Session Variable
            Session[PROCESS_NAME] = false;

            //Create and initialize new thread with the 
            //address of the StartLongProcess function
            Thread thread = new Thread(new ThreadStart(StartLongProcess));

            //Start thread

            //Pass redirect page and session var name 
            //to the process wait (interum) page
            Response.Redirect("ProcessingMessage.aspx?" + 
              + PROCESS_NAME);

        private void StartLongProcess()
            //Replace the following line of code with your long process
            Thread.Sleep(Convert.ToInt32(this.txtProcessLength.Text)* 1000);

            //Set session variable equal to true when process completes
            Session[PROCESS_NAME] = true;


The ProcessingMessage.aspx page is used to inform the user how long he/she has waited and redirects the user to the specified page when the long process is complete. With the source code, I've included a simple yet effective animated gif called Processing.gif that's used to simulate a process occurring in the background. I've also forced the page to refresh every second by adding the equiv-refresh meta tag to the aspx portion of the Web form.

<meta http-equiv="refresh" content="1">

In the Page_Load method, I am setting a session variable called Session["ProcessTime"]. This variable is used to keep track of how long the process has been running and display this to the user. Every time the page refreshes, Session["ProcessTime"] is incremented by 1.

Session["ProcessTime"] = Convert.ToInt32(Session["ProcessTime"]) + 1;

You'll also notice that I'm checking the state of the session variable that's waiting to be set on the triggering page. Once this variable equals true, I set both the Session[processSessionName] and Session["ProcessTime"] equal to null and redirect the user to the page specified in the querystring. I set the session variables equal to null in case the user performs another long process within the same session.

using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;

namespace AsynchronousProcessing
    public class WebForm1 : System.Web.UI.Page
        protected System.Web.UI.WebControls.Label StatusMessage;
        private void Page_Load(object sender, System.EventArgs e)
            string redirectPage = Request.QueryString["redirectPage"];
            string processSessionName = Request.QueryString["ProcessSessionName"];
            if (Session["ProcessTime"] == null)
                StatusMessage.Text = "Process has been running for 0 seconds";
                Session["ProcessTime"] = 0;
                Session["ProcessTime"] = Convert.ToInt32(Session["ProcessTime"]) + 1;
                StatusMessage.Text = "Process has been running for " + 
                        Session["ProcessTime"].ToString() + " seconds";

            if ((bool)Session[processSessionName] == true)
                Session[processSessionName] = null;
                Session["ProcessTime"] = null;


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

Brandon Noffsinger
Web Developer
United States United States
I don't really have much to say at this point. I promise to update this if I come up with another article to submit.

Comments and Discussions

GeneralWell done - great sample [modified] Pin
Taner Riffat24-Apr-10 2:00
MemberTaner Riffat24-Apr-10 2:00 
GeneralDoesn't work in 3.0 Pin
csandvig16-Jun-08 7:44
Membercsandvig16-Jun-08 7:44 
GeneralRe: Doesn't work in 3.0 [modified] Pin
Taner Riffat24-Apr-10 1:58
MemberTaner Riffat24-Apr-10 1:58 
Generalhuge problem Pin
Gevorg30-Oct-07 5:03
MemberGevorg30-Oct-07 5:03 
GeneralRe: huge problem [modified] Pin
Taner Riffat24-Apr-10 2:02
MemberTaner Riffat24-Apr-10 2:02 
GeneralVery Nice Pin
Zeeshan Reyaz3-Oct-07 2:14
MemberZeeshan Reyaz3-Oct-07 2:14 
QuestionHow do I get information back from the... Pin
travich5-Jan-07 19:26
Membertravich5-Jan-07 19:26 
AnswerRe: How do I get information back from the... Pin
ph0o4-Sep-07 3:16
Memberph0o4-Sep-07 3:16 
GeneralMy thread doesn't even appear launtched Pin
Andre Dias1-Jan-07 23:06
MemberAndre Dias1-Jan-07 23:06 
QuestionWhat if I don't want a wait page? [modified] Pin
EnoughToBeDangerous23-Aug-06 4:27
MemberEnoughToBeDangerous23-Aug-06 4:27 
GeneralLosing Session Problem Pin
MickAllen24-Mar-06 10:16
MemberMickAllen24-Mar-06 10:16 
GeneralHaving a problem with view state Pin
sombra2137-Mar-06 10:44
Membersombra2137-Mar-06 10:44 
GeneralRe: Having a problem with view state Pin
namenotchosen12-Apr-06 5:37
Membernamenotchosen12-Apr-06 5:37 
GeneralRe: Having a problem with view state Pin
OzSoft Solutions25-Apr-06 15:47
MemberOzSoft Solutions25-Apr-06 15:47 
GeneralRe: Having a problem with view state Pin
oleano29-Mar-07 11:32
Memberoleano29-Mar-07 11:32 
GeneralProblem Pin
Beetle5429-Aug-05 10:55
MemberBeetle5429-Aug-05 10:55 
GeneralRe: Problem Pin
Brandon Noffsinger29-Aug-05 11:05
MemberBrandon Noffsinger29-Aug-05 11:05 
GeneralLittle problem in vb Pin
Lumenm16-Aug-05 4:05
MemberLumenm16-Aug-05 4:05 
GeneralRe: Little problem in vb Pin
Brandon Noffsinger16-Aug-05 4:56
MemberBrandon Noffsinger16-Aug-05 4:56 
GeneralRe: Little problem in vb Pin
Lumenm16-Aug-05 5:32
MemberLumenm16-Aug-05 5:32 
GeneralRe: Little problem in vb Pin
Lumenm18-Aug-05 1:38
MemberLumenm18-Aug-05 1:38 
Generalthreading error Pin
Lumenm18-Aug-05 23:06
MemberLumenm18-Aug-05 23:06 
GeneralRe: threading error Pin
Brandon Noffsinger19-Aug-05 5:40
MemberBrandon Noffsinger19-Aug-05 5:40 
GeneralRe: threading error Pin
Lumenm19-Aug-05 10:02
MemberLumenm19-Aug-05 10:02 
AnswerRe: threading error Pin
Lumenm15-Sep-05 5:50
MemberLumenm15-Sep-05 5:50 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.