Using this configuration inheritance can generate a problem that occurs when you host an ASP.NET application in the root folder and add a subdirectory with another ASP.NET application. This way, all settings that are set above your subdirectory application are applied to your child application as well, which may cause it to malfunction.
In Sitefinity CMS context, it is not sufficient to use <location inheritInChildApplications=”false”> - you must also add the <clear> and <remove> tags in the web.config file of the child application. Use the following example:
The rest of the web.config nodes are inherited from the parent Sitefinity CMS site, therefore, in the child application we need to include or exclude all additional or unnecessary config elements.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity