> So, basically, if I don't want to rethink and rebuild my > whole development environment, I should stick with good 'ol > Application.CFM?
I guess, but in any case, your development environment should match your production environment as closely as possible. If things like file paths aren't very similar, you should probably rethink and rebuild your whole development environment accordingly, or abstract away those differences using things like mappings. > It seems indeed that "you can't" is the answer here, but > shouldn't it be possible to do that? > Is there a good reason for not having relative path support > (and I mean "../", Will) for extending components? I suspect it works this way for the same reasons that it works this way with every other compiled OO language I've seen that lets you define classes and extend them. I'm not knowledgeable enough about compiler design to explain why that is, though. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307410 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
