Surprisingly, this is such a situation in which I played so here are some tips.
- As you probably understood, perhaps by looking at the CF code, the whole language structure is prefixed with
cf (I think this may not be a very pimped way to advertise Adobe ...) - Architecture Define the architecture of an existing CF application. eg. It is based on MVC using a framework like Fusebox. The reason for this is that it can help you understand what the result of an asp system should be architecturally.
- Language / Syntax Guidelines - CF is pretty easy to understand, and if you're not using the Adobe online link. CFCs (ColdFusion components) are similar to classes.
- Variables - see here. I have been burned many times while working on CF applications. Knowing the string vs int.
- Web Services CF allows a very simple announcement / creation of web services. Check all your
cffucntion properties to identify them ( access="remote" ) cfquery . The worst and best in CF imo is cfquery . Not the function itself, but the way it is used in the current application. CF has no limits on what you can do, and where you can do it, to find random requests scattered throughout the application. It's a double sword function .
The above is noted as a result of work on a poorly developed CF application. Nevertheless, from the point of view of functionality and performance, it is rich, full of opportunities and pleasure for work.
EDIT
I found the following resources that may be of interest if you have not found it yet
If I come up with anything else, I will update.
Ahmad source share