Aholics.com
Active member
Hi folks,
I'm using an existing web application that has URL Rewriting built into it. I've modified it to suit my needs and it works perfectly under the built-in Visual Studio Web Server...but it won't work in IIS 6.
I'm in the middle of migrating from one forum package (Classic ASP) to a new one (ASP.NET). In doing so, I've got a DB that maps old User, Topic, Reply, IDs to new ones and performs a permanent redirect. In the development environment, the URL Rewriting engine (ASP.NET) takes the Classic ASP request and processes it appropriately.
In IIS 6, I've configured the forum application directory to use the ASP.NET DLL for any .asp page requests (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll). However, the global.asax file isn't even firing when the request to the .asp page is made. I simply get a 404 error.
What am I missing here? Going a bit crazy with this one...
Thanks!
AL
I'm using an existing web application that has URL Rewriting built into it. I've modified it to suit my needs and it works perfectly under the built-in Visual Studio Web Server...but it won't work in IIS 6.
I'm in the middle of migrating from one forum package (Classic ASP) to a new one (ASP.NET). In doing so, I've got a DB that maps old User, Topic, Reply, IDs to new ones and performs a permanent redirect. In the development environment, the URL Rewriting engine (ASP.NET) takes the Classic ASP request and processes it appropriately.
In IIS 6, I've configured the forum application directory to use the ASP.NET DLL for any .asp page requests (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll). However, the global.asax file isn't even firing when the request to the .asp page is made. I simply get a 404 error.
What am I missing here? Going a bit crazy with this one...
Thanks!
AL