ASP.NET applications correspond to IIS applications, which are on a per-folder basis. IIS application architecture is not designed to have two different applications running in the same folder; you need to create a virtual directory underneath your main application. If you remove the web.config and global.asax files from your 2nd application, it should look to the parent application for those files.
Edit: RE your additional details – simply create a new virtual folder underneath your main IIS site, and put your application in there.
Or, maybe I am misunderstanding the problem. Do you want to have two root-level applications? If so, you can simply create more IIS websites and assign specific HTTP headers to each one (for example, aaa.com to site 1 and bbb.com to site 2; IIS will route the requests to the correct site, even though both domains point to the same IP).
Comments
Leave a comment Trackback