Currently we have TS 6.7.2 and 7.2.1 on Windows 2003 and IIS 6.0. We're migrating to TS 7.3.1 and LSDS 7.3.1. But we'll remain on Windows 2003 and IIS 6.0 (in both the Authoring and Runtime environments).
We have a bunch of legacy ASP pages in TS 6.7.2 that we want to gradually migrate to LiveSite. Meanwhile, we took a section of those ASP pages and created a SitePublisher/LSDS site with it.
Now we want to serve both the old ASP pages and the new .page files via 1 IIS 6.0 instance of LSDS for .Net. (This way, we can have a single domain name for our end users to access the various sections of our Web site.)
However, the "Web Solutions Runtime Components 7.2. Installation Guide" says the following in the “Configure Microsoft IIS 6 on Windows 2003” section of the "Configure LSDS for .Net" chapter:
In the IIS Manager, configure the LiveSite Runtime Web site with the following settings: In the Mappings tab, copy the .aspx extension path and add it as a wildcard application map (clear the Verify that file exists check box).
But that redirects all the pages to aspnet_isapi.dll, thereby rendering the ASP pages (which are supposed to be handled by asp.dll) blank.
So, in IIS, we removed the wildcard application map above and, individually associated aspnet_isapi.dll with the following extensions: “.page” and “.site.”
We're having better results with ASP pages now, and can render .page pages too.
Not all is well, though. For example:
http://localhost/ is not working now; before, we got a list of LiveSite sites to choose from.
http://localhost/mysite/mydir/ is not working now; before, we got a list of LiveSite sites to choose from.
http://localhost/sitealias is not working now; before we got /mysite/default.page
What other extensions should we map to aspnet_isapi.dll? Or, should we be updating the Web.config file instead? If so, how?
Thoughts?
Many thanks,
Sunny Wan
