I am trying to add an application within the Umbraco directory. This application is not directly related to Umbraco, but web.config settings are being applied to the sub-app because that's just how that works. I know I can use <location> to stop config inheritance, but I'm not sure where to apply it.

When the sub-app tries to load, it throws "Object reference not set to an instance of an object." from "Umbraco.Web.UmbracoModule.BeginRequest". Looking at other posts, I see I can get around this by changing the sub-app's global.asax to inherit from Umbraco, but I don't think I want that. Would that not stop the sub-app from working?

Is there a setting I need to add <location> to in the parent Umbraco web config to stop this behavior from attempting to happen? How do I stop the parent Umbraco app from trying to initialize itself in the sub-app?

I did go down the path of inheriting from Umbraco in the sub-app's global.asax. This led me to an error where Umbraco is trying to redirect to config/splashes/noNodes.aspx. The only reference I see to that in web config is an entry in umbracoReservedUrls.

I guess what I'm getting at is that I'm unsure how to turn off Umbraco in a sub-app within the Umbraco directory. I've added the sub-app's path in reserved URLs, but that doesn't seem to work either.