How to work withLong Running Processes using ASP.NET with C#

I want add item in a list or datatable object and save it in database but due to some check condition with useing for loop/ foreach it's take long process for complete it so many time it's failed so how to manage it.

Ex: You want doctor appointment schedule using with asp:calender controls...

Thanks7872 14-Aug-14 3:04am

You have already been advised how to manage it. Now its your turn to understand and implement it.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manfred Rudolf Bihy · Accepted Answer · 2014-08-13T02:46:00

Don't do it directly from the webpage is my advice. Why is that so, you might ask. Simples:
Worker processes are recycled regularily and thus your threads will also stop running and you won't even know how much of the work has been done and where to resume (if this has been coded into the solution at all). One might counter that it is possible to start a separate process from the webpage, which is a bit better, but is still lacking.
Starting a separate process will allow it to stay alive even when the worker process(es) get restarted, but the knowledge about an ongoing operation will somehow have to be restored once the workers have been restarted. So what you really need is an intermediary process that allows you to start processes/threads, pass parameters to them and receive return values.
The intermediary process will do the house keeping, starting the processes/threads, keeping track of a process' / thread's progress and keep the results around until they can be delivered/returned to the worker process (in case you don't know: The worker process(es) are where the webpages are run in ASP.net).

A whole other issue when going without an intermediary process is what happens when high load is put onto the system. If a lot of extra processes are started you might cripple your webserver. The intermediary process can be programmed to only start a number of processes/threads and then wait until one terminates before starting the next request from the queue. It can also be used to offload this processing to other servers so the systems with the IIS and the application on them stay responsive.

Cheers!