disabling web.config inheritance
- From: "apiringmvp" <bdewey01@xxxxxxxxxxx>
- Date: 12 Jul 2006 18:54:55 -0700
Hey everyone,
I have a config file issue. I have a website with a front in and a
back end. (eg. http://www.site.com/ and http://www.site.com/admin).
They are both written in .NET 2.0 using C#.
I am having conflicts on the web.config settings. my exact message
right now is:
"This application was precompiled with personalization turned off, but
it appears to have been turned on after the precompilation, which is
not supported. "
I am assuming that is occuring because, the root application doesn't
have any themes set up, while the admin site does. I am also have some
conflicts between connection strings, profile and membership providers,
because each site has a different one.
If I publish the two sites to different (eg. http://www.site.com/root
and http://www.site.com/admin) everything works, except the images
don't work because they are looking for ../product_images.
Question:
- is there a way to globally disable inheritance on themes/profiles
and membership settings? or force it to use the admin config over the
root?
- if not, is there a way to set the root site to theme="" and override
that in the admin?
- Ben Dewey
.
- Follow-Ups:
- Re: disabling web.config inheritance
- From: Nathan Sokalski
- Re: disabling web.config inheritance
- Prev by Date: Re: how to open second window and resize it
- Next by Date: Re: Or the UGLY or the ERRONEUS one ?
- Previous by thread: firing IE transition effects to smooth classic DataGrid paging events?
- Next by thread: Re: disabling web.config inheritance
- Index(es):
Relevant Pages
|
