Thanks for making me think about my response. <grin> I actually didn't
even mean exception, infact after reading my response, I think I just
randomly typed something in that sounded good...
Not all threads in a asp.net application have a HttpContext.Current attached
to it. You can use the HttpContext.Current if you want to know if the
calling thread ( current context) is currently processing a request through
the Http Pipeline, but it is not a reliable indicator that the calling
assembly is a windows application, or a web app. Timers, callbacks, user
created threads, etc will have a null value and can be from either.
Thanks for straightening me out Scott!
bill
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:cs********************************@4ax.com...
bill:
I think you meant to say "yield a compiler error", not "throw an
exception exception"....
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Thu, 10 Mar 2005 14:08:08 -0600, "William F. Robertson, Jr."
<th****@nameht.org> wrote:
Be aware if your solution doesn't have a reference to System.Web.dll, it
will throw an exception if you access System.Web.HttpContext.
bill