ASP.NET healthMonitorin g WebErrorEvent / IIS7

[Howard Hoffman]

We've an ASP.NET 2.0 application that we're migrating to IIS7 and W2K8.

We have application that makes heavy use of the
System.Web.Mana gement.WebError Event type to Raise() errors to the configured
ASP.NET health monitoring providers. This has proven to be a good solution
for us over the 3 years the application has been in production.

Our application has logic that fires in the Global.asax Application_Sta rt
event, and that logic also uses the WebErrorEvent type to Raise error
events. This does not work in IIS7 for an Integrated applcation.

In my view, this is a fixable limitation that MS should address and release
as a patch.

The issue is that System.Web.Mana gement.WebReque stInformation class (it is
marked Internal according to Reflector) makes an illegal (when called in the
context of an Application_Sta rt event) call to HttpContext.Cur rent.Request.
Ironically, the WebRequestInfor mation class does already handle the case
where HttpContext.Cur rent is null, and proceeeds normally after that point.

What happens is that our application only cannot Raise WebErrors
appropriately within Application_Sta rt.

In our case, we're using 3 Providers:

Event Log Provider
SQL Web Event Provider
Templated Mail Web Event Provider

I'm looks to me (again, via Reflector) that all 3 would work just fine
without a live HttpContext.Cur rent.Request.

What is Microsoft's plan for updating System.Web.Mana gement to work in this
case? What is a recommended practice that developers should follow here?

Thanks in advance,

Howard Hoffman

[=?Utf-8?B?YnJ1Y2UgYmFya2Vy?=]

it looks like a simple bug. you should open a support call.

-- bruce (sqlwork.com)
"Howard Hoffman" wrote:

We've an ASP.NET 2.0 application that we're migrating to IIS7 and W2K8.

We have application that makes heavy use of the
System.Web.Mana gement.WebError Event type to Raise() errors to the configured
ASP.NET health monitoring providers. This has proven to be a good solution
for us over the 3 years the application has been in production.

Our application has logic that fires in the Global.asax Application_Sta rt
event, and that logic also uses the WebErrorEvent type to Raise error
events. This does not work in IIS7 for an Integrated applcation.

In my view, this is a fixable limitation that MS should address and release
as a patch.

The issue is that System.Web.Mana gement.WebReque stInformation class (it is
marked Internal according to Reflector) makes an illegal (when called in the
context of an Application_Sta rt event) call to HttpContext.Cur rent.Request.
Ironically, the WebRequestInfor mation class does already handle the case
where HttpContext.Cur rent is null, and proceeeds normally after that point.

What happens is that our application only cannot Raise WebErrors
appropriately within Application_Sta rt.

In our case, we're using 3 Providers:

Event Log Provider
SQL Web Event Provider
Templated Mail Web Event Provider

I'm looks to me (again, via Reflector) that all 3 would work just fine
without a live HttpContext.Cur rent.Request.

What is Microsoft's plan for updating System.Web.Mana gement to work in this
case? What is a recommended practice that developers should follow here?

Thanks in advance,

Howard Hoffman