Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Greetings folks,
The ASP.NET application I’m maintaining has a fairly long start up procedure. A number of data files are updated, etc. I’ve been asked if there is a way for the application to return a wait screen (static if necessary) while Application_Start is running?
No, there’s not. ASP.Net needs to initialize the pipeline and everything else just to get to the point of being able to actually handle the request.
Prior to that point, .Net has no idea what the request is, nor what the potential outcome might be. For example, it might be a web service call which has no response. Or the request might cause a document to download at which point you don’t want to have any data sent to the client yet.
Instead, I’d look into two things. First, how to reduce the app_start time; and, second, why would an application_start event be kicked off more than once in a blue moon.