Think of ASP.net as a whole different language and paradigm than straight ASP. In fact, as a framwork, ASP.net looks and feels quite a bit like Flex. Good ASP programming with use a combination of code-behinds in vb script, C# classes that are inheareted into the ASP.net page and stored proceedures for accessing data, and custom componet tags.

With that out of the way here are some of the more compelling reasons to use CF.

1) Cold Fusion is not tied down to the Windows platform. ASP.net is definatly tied to the whims of microsoft. In fact you can run Cold Fusion in a Linux/Apache/Tomcat environment. The last time I checked, these systems were free.

Windows as the operating system can cost anywhere from a few hundred to a few thousand dollars depending on the version selected. Linux/Apache/Tomcat can be downloaded for free.

In fact, if cost were the only issue, take a look at Jarkarta Struts -- a Java framework containing many of the same features as ASP.net. Since your team is not considering Struts --this tells me that cost is not the only issue here, rather your team wants to use the Microsoft platform.

2) ASP.net is tied to the current version of the IIS webserver. I do not believe you can use the Apache webserver with ASP.net. In fact Microsoft considers IIS an application server for ASP.net.

>hi guy
>   
>   Can someone give me advantage/disadv in asp.net and
>coldfusionmx?.
>asp.net is free? or how much?. I current have
>coldfusionmx and try to convince some of my coworkers
>to use coldfusion
>
>thanks
>John
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Win a $20,000 Career Makeover at Yahoo! HotJobs  
>http://hotjobs.sweepstakes.yahoo.com/careermakeover
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to