New and Improved Holy Grail

In my previous blog, I discussed a method for overcoming the lack of an HTTPContext for scheduler tasks.  While the code works, I was a little leary of it because of some questions about changing current appDomain data using the Thread.GetDomain.SetData method calls.  Specifically in my previous blog I discussed setting the appPath to nothing so that we could successfully call the SimpleWorkerRequest constructor.  Well after futher thought and reflection, I realized that this is not necessary.  It is possible in a multi-threaded environment (which clearly is the case with the web and the scheduler) for this value to be set to nothing and then for another thread to attempt to use this value before it can be reassigned later in my method.  I am unsure of the consequences of this action but think the results would not be good.

In light of this I have gone back to the drawing board.  Below is a simplified SetHttpContextWithSimulatedRequest method:

In this case I don't have to worry about the values I am using because they are values that are already being used by the HttpRuntime and therefore shouldn't be overwriting some other critical values (e.g. we are not creating a virtual directory for the appDomain that is different from the current virtual directory).