We are in the process of upgrading our operating system from Windows XP to Windows 7. Our developers need to run applications locally on their computer before deploying them to the live site.
Before converting our apps to ASP.NET, we'll have to maintain our current Classic ASP applications. Currently we have several Classic ASP applications that have server side include files (SSI) that use the asp file extension. This has prevented spaghetti code and makes the code more manageable.
I've configured IIS7 to process classic asp pages, but need to know how to configure IIS7 so that the asp include files are recognized as SSI files and are processed accordningly.
I tried the Add Module Mapping, as described in the official IIS website, but that didn't work.
Before converting our apps to ASP.NET, we'll have to maintain our current Classic ASP applications. Currently we have several Classic ASP applications that have server side include files (SSI) that use the asp file extension. This has prevented spaghetti code and makes the code more manageable.
I've configured IIS7 to process classic asp pages, but need to know how to configure IIS7 so that the asp include files are recognized as SSI files and are processed accordningly.
I tried the Add Module Mapping, as described in the official IIS website, but that didn't work.