Last post Apr 23, 2009 04:58 PM by Bruce L
Apr 22, 2009 02:52 PM|mnswiftone|LINK
My hosting company provides Shared SSL and I have it working fine for my primary site.
I also had an Adminstration web site in a folder under the primary site - and since updating to 2.0 it no longer functions - cannot even load a page. I think I read somewhere that under 2.0 the root web.config overrides all sub-dir web.configs and thus can
no longer support sub-dir sites.
<host>\httpdocs folder contains site - is the current virtual dir of my site i.e.
<host>\httpdocs\Admin used to work as my admin site on a prior host under 1.1. This folder had its own web.config and related Bin, App_Code etc.
The shared SSL virtual dir 'SSecure' points to <hostname>\currentsite.com
- this results in the site being loadable via
The Admin site used to be accessed via:
http://<hostname>/SSecure/Admin/login.aspx but this cannot even be seen now with 'no resources found error'.
I also could just login via currentsite.com/Admin/secureadmin.aspx and it would act as its own site and redirect to the https login page.
Does anyone have any ideas on how I can arrange this hosted site to support two separate sites under one directory?
I have asked the hosting company but no response yet - about this idea:
Repoint the primary site virtual dir to \httpdocs\Main as the main site dir
Point a second site virtual dir to \httpdocs\Admin as the admin site dir
Then, in theory - each would still be under the same Shared SSL - both in independent directories so separate sites?
I could then SSL into
Does this sound possible to work under .NET 2.0/3.5 ???
Any other ideas besides buying another site - I really want to keep the admin site separate from the consumer site.
Apr 22, 2009 05:56 PM|Bruce L|LINK
I think the problem is related to web.config inheritance.
Since your root application, /, is set to 2.0 and the web.config most likely contains asp.net 2.0 attributes, the sub directory, /admin, will inherit these settings. If the sub directory is configured to run asp.net 1.1, it will treat those 2.0 elements
as invalid and thus throws an error.
You can try disable inheritence from your root application. See http://www.aspdotnetfaq.com/Faq/how-to-disable-web-config-inheritance-for-child-applications-in-subfolders-in-asp-net.aspx
Apr 23, 2009 04:19 AM|HostingASPNet|LINK
Also both applications should be .NET 2.0, because it's not possible to be in the same application pool if the one is 1.1.
Apr 23, 2009 08:58 AM|mnswiftone|LINK
Apr 23, 2009 04:58 PM|Bruce L|LINK
setting the /admin directory to an IIS app should fix your problem.