In a webapplication, a regular foreground process is bound to get a script timeout if some task takes too long. One can influence the moment of that timeout by setting HttpContext.Current.Server.ScriptTimeout to some high(er) value.
But what about processes that are setup to run in the background as asynchronous operations or on manually started new threads? Must one also set the ScriptTimeout for these background processes, or can they run "forever"?
And if a timeout must be set to high value explicitly for a long running process, how can that be done (since HttpContext.Current is not available then)?
...
Go to the complete details ...