We recently ran our own servers and are moving all of our applications and websites to DiscountASP. We will be running several small ASP.NET 2.0 applications within each hosting package that cannot be run in the same directory. We had previously mapped them in IIS with separate IP's and sub domains to their own root directory. Our goal is to use the Web Application Tool and sub directories for multiple applications. We don't believe pointing will be an issue as we can use sub domains and redirect to the directories or just use the path to the files in each sub directory. PROBLEM: Currently in the virtual DiscountASP environment, we are able to run the applications at the root, but not in the sub directories using the Web Application Tool. The applications will run one at a time on the root directory, but we need each application loaded into their own directory and should not be combined to the same directory. We tried the subdirectory and applied the Web Application Tool. We then moved the files to the sub directory. We hit the default file and we get 404.0 as the application continues to inherit the path to the root directory. I see where the Web Application Tool modified or added a web.config file, but I’m not sure actually when these applications were first coded. The files appear to be are ASP.NET 2.0, but still use global.asa. Does anyone have any suggestions or script to configure applications written in this version to seek the root to run in the subdirectory? I looked at Visual Studio ASP.NET Web Site Administration tool, but I’m still searching …. Please help or shoot me in the right direction. Thanks. Kevin
Hi, You seem to have a handle on this but didn't mention root inheritance. Search the ASP.NET forums and Scott Guthrie's blog for some good tips on overriding root inheritance. You can definitely do this bu the concerns will be: 1) Make sure the sub-folder for each app is using an application you created in the control panel. 2) Use any tricks you find for overriding asp.net root web.config inheritance. 3) Maintaining older versions of .NET All the best, Mark
