ASP vs Cold Fusion

[brockj]

I am working on a project, we have Cold Fusion in house however, I am not very good with it. I realize there are benefits, however, I feel ASP would be a better approach to many of the current and upcoming projects. To list out a few of the projects:

Dashboard
Help Desk/Ticket
Task List (will be similar to help desk)

The Cold Fusion that we have in house is the standard edition so there is no active directory integration (that I know about), and I am thinking with the help desk software that would be very nice. I am currently not doing ASP.NET, but can't beleive it to be that difficult to go to if need be.

So give me your opinions please! And if you have any info to back it up all the better!

 

[Unheard]

CF Standard supports AD without issues.

http://www.adobe.com/devnet/se..._active_directory.html

The only other issue you present is your knowledge of CF. When it comes down to it, the choice between ASP or CF is 6 in one hand, a half dozen in the other. I'd say go with what your comfortable with and what you can develop quickest with.

 

[hooflung]

They work equally well. Dot Net is free for what its worth. At the end of the day, Cold Fusion is more exotic and more webcentric but dot net has more to offer for the complete package if you want to turn code from webforms to windowforms for individuals who need a tool on the intranet to be put on their laptop while away.

 

[bsobel]

Originally posted by: hooflung
They work equally well. Dot Net is free for what its worth. At the end of the day, Cold Fusion is more exotic and more webcentric but dot net has more to offer for the complete package if you want to turn code from webforms to windowforms for individuals who need a tool on the intranet to be put on their laptop while away.

Coldfusion was great before and blew away ASP 1.0. However IMHO now that we have ASP 2.0+ it's the better choice.