我们正在从 asp classic 迁移到 .net。 不幸的是，他们将所有 .asp 文件命名为 .aspx，以便在迁移到 .net 时不会失去页面排名。 这意味着 IIS 将所有 .aspx 文件映射到 asp.dll。
更改回映射后，我将尝试让处理程序抓取请求，然后检查文件中是否有任何 vbscript，然后将其返回给 asp.dll（如果它继续正常处理请求）。
我们使用的是IIS7。
我认为也可以使用 ISAPI 过滤器来实现此目的，但随后我必须学习如何为 IIS7 制作 ISAPI 过滤器（如果在 .net 中没有办法实现此目的，则可以）
有想法吗？ 谢谢！！
We are migrating from asp classic to .net. Unfortunately they named all of the .asp files as .aspx so that they wouldn't lose page rank when they moved to .net. This means that IIS maps all .aspx files to asp.dll.
After changing the mapping back I was going to try have a handler grab the request then check if there is any vbscript in the file and then hand it back to asp.dll if it otherwise proceed to handle the request normally.
We are using IIS7.
I think it may be possible to use a ISAPI filter to this too, but then i would have to learn how to make an ISAPI filter for IIS7 (which is fine if there isn't a way to this in .net)
Ideas? Thanks!!
发布评论
评论（1）
恕我直言，您最好使用 ATL Server 支持库并制作 ISAPI 过滤器。请参阅： http://msdn.microsoft.com/en-us/library/2chz4bx6(VS.80).aspx
另外你真的不想点击 aspnet_isapi.dll 除非您知道您需要 ASP.NET 处理； 为什么会受到打击？
虽然我可能没有正确理解你的问题...你是否在同一个应用程序中混合经典 ASP 和 ASP.NET ？ 如果您必须在两者之间共享会话状态，这可能相当具有挑战性......
IMHO you would be better off to use the ATL Server support libraries and make an ISAPI filter.See: http://msdn.microsoft.com/en-us/library/2chz4bx6(VS.80).aspx
Plus you really don't want to hit the aspnet_isapi.dll unless you know you need ASP.NET processing; why incur the hit?
Although I may not understand your question correctly... Are you mixing classic ASP and ASP.NET in the same application? If you have to share session state between the two this can be rather challenging...