As a CF veteran (tagging since 3.0), I have to put in my EUR.02 here.
ASP, as everyone knows and loathes it, is history.
Sure there are maintenance jobs to do, but that's irrelevant.
The real discussion should be about CF versus ASP.NET. One class ought to be enough to convince you that the .NET monster is the wave of the future. Robust? Holy moley, is it robust. Scalable? Off the scale. Flexible? Rapid, built in conversion to a Web Service, to a Windows app, to what you need. True XML manipulation, not this bass-ackwards WDDX stuff.
What I never understood about CFMX is why the heck they decided 1) to introduce another layer in the data connectivity area (Java? we don't need no stinking Java!); 2) to trash, no, mutilate, a perfectly good development environment; 3) to drop DSN-less connections after v5 (duh!); and 4) to bury the command-line utility.
Take a stroll through the MacroMedia CF forum, and gawk at the ton of problems associated with this J2EE nonsense. It's enough to make us come to a screeching halt in our upgrade path, right before the cliff that is CFMX. My little ol' 4.5.2 apps are humming along just fine, thank you.
Maybe, just maybe, they'll turn it around with the next upgrade, but I'm not holding my breath. I have to design my next ASP.NET app.
(And it's a shame that it had to come to this....)
PH