In IIS you can add virtual directories. In IIS context, such a directory is a subfolder, but it does not physically exist in the parent website. It is useful for sharing resources, such as CSS, JavaScript, Images, Videos, etc. across multiple websites.
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.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important