Wow, that's some undertaking. I developed in Cold Fusion 3 and 4 for a
couple of years before moving to ASP and eventually ASP.Net.
Apologies if I am stating the obvious but the two are fundamentally
different languages, cold fusion is a script based language that blurs
the boundaries between code and presentation whereas .Net encapsulates
the two occording to the rules of object orientation
The first thing I'd do is analyse all the sql used in the coldfusion
site and if its in line get it shifted to stored procs.
Now you could go for a half way house solution and shift the cold fusion
logic into the .aspx pages themselves but it should really sit in the
code behind files - it depends how long you have to migrate the project.
*** Sent via Developersdex
http://www.developersdex.com ***