Have we ever had a satisfying explanation for why we can have relative
paths "down" the directory tree but not "up" the directory tree?
That would solve this problem (and many others) without needing dynamic
run-time evaluation of CFC paths.
Mark Mandel wrote:
Yeah... good luck with this one - it's just he bane of most CFC
developer's existence.
Although not a supported feature, you can always try using relative CFC typing -
http://www.compoundtheory.com/?action=displayPost&ID=56
That way if you move your code, it will work just fine.
Otherwise, nope, there is no way of getting around this issue.
I'd suggest writing some sort of installer for each app dev,stage,prod
that replaces something like %cfcRoot% as the correct value. Yuck I
know, but that's about the best idea there is if you don't wanting to
use the relative markup.
Just some thoughts.
Mark
On 6/8/05, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote:
I was looking for a "in the mean time" approach I could take well trying to
tie in a new chunk of code into the old infrastructure.
-Dan
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
