I
Ian McCullough
I develop and maintain an application that takes advantage of ASP.NET hosting
internally. More explicitly, its an ASP.NET application that creates
instances of its own pages internally (GetCompiledPageInstance) to do
one-time meta-data collection.
After installing KB886903, all calls to GetCompiledPageInstance die with
HttpException in a function called
System.Web.HttpApplication.CheckSuspiciousPhysicalPath. There doesn't seem
to be anything wrong with the virtual or physical paths getting passed in, so
I'm at a loss to know how to proceed. Uninstalling KB886903 solves the
problem for now, but isn't a long term solution in my eyes.
Can anyone out there shed some light on this?
Thanks
Ian
internally. More explicitly, its an ASP.NET application that creates
instances of its own pages internally (GetCompiledPageInstance) to do
one-time meta-data collection.
After installing KB886903, all calls to GetCompiledPageInstance die with
HttpException in a function called
System.Web.HttpApplication.CheckSuspiciousPhysicalPath. There doesn't seem
to be anything wrong with the virtual or physical paths getting passed in, so
I'm at a loss to know how to proceed. Uninstalling KB886903 solves the
problem for now, but isn't a long term solution in my eyes.
Can anyone out there shed some light on this?
Thanks
Ian