I've seen an email from Piers Williams in december asking about this.
Basically - in an ASP.NET application - none of the existing contexts
are safe to use.
I'd like to remedy this. There are two ways forward that I can see.
1. Add a new WebContext class.
2. Change the ThreadLogicalContext
Yep - Thats the email I was talking about.
Thanks for the reply.
j.
Sorry, I blanked and completely glazed over the first line of your email. :)
-Chad
On 2/15/06, josh robb [EMAIL PROTECTED] wrote:
Yep - Thats the email I was talking about.
Thanks for the reply.
j.
I don't think HttpContext is always available...especially inside the
Global.asax.cs methods and/or inside CacheItemRemovedCallback methods.
According to this article:
http://www.odetocode.com/Articles/112.aspx
HttpContext is just a wrapper around
System.Runtime.Remoting.Messaging.CallContext.
