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.HttpApplication,
Global.asax uses it).

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

Page Error Handler

public class PageBase : System.Web.UI.Page {
protected override void OnError(EventArgs e) {
HttpContext ctx = HttpContext.Current;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.HttpApplication {
protected void Application_Error(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Current;
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********@avansoft.com> wrote in message
news:uX**************@TK2MSFTNGP09.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.HttpApplication,
Global.asax uses it).

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

Page Error Handler

public class PageBase : System.Web.UI.Page {
protected override void OnError(EventArgs e) {
HttpContext ctx = HttpContext.Current;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.HttpApplication {
protected void Application_Error(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Current;
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.rilling.net> escribió en el mensaje
news:%2****************@TK2MSFTNGP15.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********@avansoft.com> wrote in message
news:uX**************@TK2MSFTNGP09.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.HttpApplication, Global.asax uses it).

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

Page Error Handler

public class PageBase : System.Web.UI.Page {
protected override void OnError(EventArgs e) {
HttpContext ctx = HttpContext.Current;
if (ctx == null) {
// is this even possible?
}
}

Application Error Handler

public class GlobalBase : System.Web.HttpApplication {
protected void Application_Error(Object sender, EventArgs e) {
HttpContext ctx = HttpContext.Current;
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?