how to convert asp to cold fusion?

An application in "simple ASP" should be straightforward to convert to CF, but it will nevertheless be a manual process.  There won't be a one-to-one correspondence between the ASP code and the CF code:  the CF equivalent is likely to be much smaller and simpler.

The difference (and the potential advantage of CF) lies in its fundamental approach to the problem:

• ASP is, well, Visual Basic.  It's a programming language by nature, and a web-page is therefore "a script."  The web-server hands the car-keys to the page (full of executable code...) and the page drives the car to its destination.
• CF is, in general, much more of a declarative language.  The various documents contain a well-defined structure ... the structure of HTML itself ... and they are parsed and processed (conceptually speaking...) by an external processor which carries out the desired action based on the overall structure of the page that it sees.  Since "most pages of a certain type are more-or-less exactly the same, and there might be thousands of them," CF gives you a few well-chosen ways to build "pages like that" and to do so quickly.  CF "already knows how to drive the car to the destination," and the stuff that you write consists mostly of details.

(I recognize that my description, above, of CF's actual modus operandi is not technically correct.  But the big-picture conceptual idea stands, and that's all I'm driving at here.)

The best way to take advantage of a tool like CF in a conversion project is, "when in Rome, do what the Romans do."  Study CF to see what it can do "quickly and easily," and adapt your project's design to shamelessly take advantage of that way.  Do not spend a lot of time trying to figure out how to "jimmy" CF so that it will do a certain thing in a certain way.

The choices that were made by CF's designers are pretty-good ones.  Although CF gives you "a full programming language if you want to use it," its greatest strength is in what you don't have to write in order to get "a certain thing" done.  If you find yourself writing a lot of programming, then you need to step-back and have another look:  "there's more than one way to do it."  CF's interpretation of a dot-NET application will be quite different from the original, and it should be.  If it isn't, you're not getting market-value out of the conversion effort.

Well, I heard Blue Dragon helps people move from ColdFusion to .NET. So maybe it can also work the other way around?

I'm not sure it "converts" any code, but I think it will allow you to execute .NET pages in what is primarily a CF server.

Then again, I don't really know what I'm talking about.

Thanks,

Mikey.

There is no automatic conversion.  Look at what the asp pages do, and write the cf code that does the same thing.