Conditions for HttpContext == null

[Luis Esteban Valencia Muñoz]

I have a 2 base classes that do error handling -- one for pages
(System.Web.UI. Page) and one for applications (System.Web.Htt pApplication,
Global.asax uses it).

Are there any situations in either of these error handlers where
HttpContext.Cur rent would be null?

Page Error Handler

public class PageBase : System.Web.UI.P age {
protected override void OnError(EventAr gs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.Http Application {
protected void Application_Err or(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// how about this situation? is this possible?
}
}
}

If the context could be null in either situation, then I wouldn't be able to
get the exception information anyway. Should I just log it and return?

[Peter Rilling]

I think one way would be when you are not running within a web site context,
just a normal application.

"Luis Esteban Valencia Muñoz" <le********@ava nsoft.com> wrote in message
news:uX******** ******@TK2MSFTN GP09.phx.gbl...

I have a 2 base classes that do error handling -- one for pages
(System.Web.UI. Page) and one for applications (System.Web.Htt pApplication,
Global.asax uses it).

Are there any situations in either of these error handlers where
HttpContext.Cur rent would be null?

Page Error Handler

public class PageBase : System.Web.UI.P age {
protected override void OnError(EventAr gs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.Http Application {
protected void Application_Err or(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// how about this situation? is this possible?
}
}
}

If the context could be null in either situation, then I wouldn't be able to get the exception information anyway. Should I just log it and return?

[Luis Esteban Valencia Muñoz]

Not in this case. ITs a web application.
"Peter Rilling" <pe***@nospam.r illing.net> escribió en el mensaje
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I think one way would be when you are not running within a web site context, just a normal application.

"Luis Esteban Valencia Muñoz" <le********@ava nsoft.com> wrote in message
news:uX******** ******@TK2MSFTN GP09.phx.gbl...

I have a 2 base classes that do error handling -- one for pages
(System.Web.UI. Page) and one for applications (System.Web.Htt pApplication, Global.asax uses it).

Are there any situations in either of these error handlers where
HttpContext.Cur rent would be null?

Page Error Handler

public class PageBase : System.Web.UI.P age {
protected override void OnError(EventAr gs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.Http Application {
protected void Application_Err or(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Cur rent;
if (ctx == null) {
// how about this situation? is this possible?
}
}
}

If the context could be null in either situation, then I wouldn't be

able to

get the exception information anyway. Should I just log it and return?