Suprisingly enough this is a situation that I have toyed with so herewith are some tips.
- As you probably figured out after maybe having looked at the CF code - everything language construct is prefixed with
cf
(I guess this may be some not so suttle way of Adobe advertising...)
- Architecture Determine the architecture of the existing CF app. eg .Is it MVC based using a framework such as Fusebox. The reason imo for this is that it can guide you towards what the outcome of the asp system should be architecturally.
- Language/Syntax considerations - CF is pretty easy to understand and if you dont the Adobe online reference is there. CFC's (ColdFusion Components) are analogous to classes.
- Variables - watch out here. I have been burnt many times when working on CF apps. Knowing whats a string vs an int.
- Web Services - CF allows for very easy declaration/creation of webservices. Check all your
cffucntion
properties to identify them (access="remote"
)
cfquery
- The worst and best thing about CF imo is cfquery
. Not the function itself but rather how its used within the current application. CF has no restrictions on what you can do and where you can it so could find random queries scattered throughout the app. This is a double edged function sword.
The above noted are as a result of having worked on a badly designed CF app. However, in terms of functionality and operability - it's rich, full of features and a pleasure to work with.
EDIT
I found the following resources which may be of interest if you have not found it already
If I think of anything more I will update..