ASP file being caught by .NET isapi
I need to serve up a few .asp pages from within my ASP.NET site.

This ASP.NET site has a handler that allows us to serve up pages out of the database instead of finding them on disk (where the .asp files are located).

The problem appears to be that the .NET isapi (C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll) is catching my request... at that point, it is going to the database and not finding the file.


My question:  why is ASP.NET catching my request?  I would think it should come in and use the proper extension mapping for .asp (C:\WINDOWS\system32\inetsrv\asp.dll).  

Is there a way to tell ASP.NET to leave the .asp files alone?
ASP file being caught by .NET isapi
===

I need to serve up a few .asp pages from within my ASP.NET site.

This ASP.NET site has a handler that allows us to serve up pages out of the database instead of finding them on disk (where the .asp files are located).

The problem appears to be that the .NET isapi (C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll) is catching my request... at that point, it is going to the database and not finding the file.


My question:  why is ASP.NET catching my request?  I would think it should come in and use the proper extension mapping for .asp (C:\WINDOWS\system32\inetsrv\asp.dll).  

Is there a way to tell ASP.NET to leave the .asp files alone?