Think I get you, and the recommended workaround is to create an ApplicationProxy.cfc (name is arbitary) in the root, with just the following:

<cfcomponent extends="Application.cfc">

</cfcomponent>

So is literally just an empty proxy to your root App.cfc. From your subfolders, you can then do:

<cfcomponent extends="ApplicationProxy.cfc"> and it'll keep searching until it finds your uniquely-named proxy in the root.

If that's what you meant to do, of course...

Ah, if it's a virtual directory you'll have problems. The ApplicationProxy is "the way" it's done, but (as you've realised) CF looks at a file-level, and is not aware of any IIS mappings.

Any reason they can't just by physical directories? Even using something like a Windows Junction is they're physically located in a different place?

Whilst an interesting idea, I'm not sure the one App.cfc to rule them all will work. One app.cfc = one Application. Therefore there's no way of all your different "applications" of having separate settings, as CF will consider them just normal subdirectories.If each site doesn't actually need different App settings that'd work, but you're combining different peoples' data into one app, which is a bit risky.

If it were me, I'd look into the physical directory idea as I suspect it'll get you the result you desire the quickest.

Not sure what the protocol for adding comments to old questions is, but I found this question while trying to find a solution to this problem. Couldn't find one anywhere, so here is the solution I have come up with:

Essentially I have multiple applications that use multiple modules, and the only differences in the module use will be determined based on the application that is pulling it in and the user session variables, etc:

http://www.myapp1.co.uk/

http://www.myapp2.co.uk/

I want them both to pull in: mymodule1 which sits outside their physical directory, so I have a virtual mapping that allows them to be used in each:

http://www.myapp1.co.uk/mymodule1/

http://www.myapp2.co.uk/mymodule1/

My physical directories are:

/sites/myapp1/

/sites/myapp2/

/modules/mymodule1/

When I am inside mymodule1 it needs to use the Application file of myapp1 or myapp2 in order to continue to use the correct session variables etc. As noted above, the search for Application cfc is done by physical directory and will not allow you to reference it by relative or full paths either if you try to use 'extends'. So, basically it's impossible for the module to pull in a different Application.cfc unless you place physical copies under each app. I really don't like code duplication, so if I can't get the physical file, I need to dynamically change the Application.cfc. Here is the solution:

Create a file in each app called ApplicationSettings.xml. Add items for whatever settings are unique to the application.

So in the xml file I have applicationSettings containing applicationName, applicationID, etc.

Before I do anything in the Application.cfc I call the xml file using:

appXML = XmlParse("ApplicationSettings.xml");

appSettings = appXML.ApplicationSettings;

I then set my unique variables using the data from the xml file rather than hard coded in the Application.cfc:

THIS.name = appXML.ApplicationSettings.applicationName.xmlText;

Application.appID = appXML.ApplicationSettings.applicationAppID.xmlText;

etc

In the module1 directory, the Application file just needs an extra bit to determine which ApplicationSettings.xml to pull:

appSettingsPath = "http://#CGI.HTTP_HOST#/";

appXML = XmlParse("#appSettingsPath#ApplicationSettings.xml");