Datagrid Girl

ASP.NET vs. Cold Fusion : ScottW's ASP.NET WebLog

http://www.houseoffusion.com/hof/body/asp.cfm
http://www.swynk.com/friends/murphy/ironic_isnt_it.asp
http://www.nwfusion.com/reprints/1123rev.html

this is old news. CF is now vers 6.1 and is quite neat.
what do I miss from the ASP world? ADO and ADO.NET's extra features - that's all

Cold Fusion great technology than asp.net

Hi Koshi,
Your comment is absolutely wrong.

Take this site down!!! It's 2007 for God's sake!!!!!!

Both are good but Coldfusion in my option has them all beat.

How is coldfusion 8.

How is coldfusion8 compared to Asp.net

Vineeth:

Even in 2007 (Robert!), ColdFusion can't really compare to .Net.  The following site offers a good rundown.

comparati.com/1131-Asp-Net-vs-ColdFusion

-nnpptt

I think it might be easier to learn ASP.Net if you are familiar with C+

For 2008 - newcomers thinking about choosing coldfusion or asp.NET you should consider that now on the coldfusion homepage there are numerous references to .NET and MS technology integrations.

You won’t be seeing integration with coldfusion on the asp.net homepage... ever

.NET is the complete solution plus your OOP code can be flipped from web site to web service, to PDA to windows apps and all you need to do is rebuild the UI because all of your OOP code is completely reusable.

My real world case study is I just completed a project where I moved a .NET Windows App's data access layer and business logic behind a .NET Web Service. Doing this allowed the application to be used over the internet of course.

This is the companies main application and the reason its a desktop app is because it does tons of document management which is best served through a desktop app.

Now, I'm going to take that same web service layer and build the customers application as an asp.net web site and all I need to do is complete the web UI.

No recoding of business logic as its all stuffed behind the web service and behind that is the data access layer.

Comparing coldfusion to asp.net is like comparing apple to oranges.

Comparing coldfusion to the .NET framework as a whole is like comparing apples to onions.

You dont need coldfusion to use .NET but based on Coldfusions homepage you need the ,NET framework to fully integrate with coldfusion.

Enough said, coldfusion is dead.

I do agree she needs to update this page or delete it.

TheDude ...you are wrong.  the comparison is between ASP and CF...not ASP.NET.  CF has been around a lot longer than ASP...about 4 years longer to be specific.  I've written in both and trust me, CF is ten times easier to develop web applications with than ASP.  I can do a query in one line with CF and that same query in ASP takes 15+ lines usually.

As far as the mention of .NET on the CF pages, um, yeah...its called interoperability because that is how CF was designed...to work with disseparate systems...unlike ASP which doesn't play well outside of Windows OS's.

This blog entry is seriously outdated. and for those who wrote about CF being dead, Adobe is releasing CF9 in the fall, with integration with RIA technologies.

As stated a year ago, ASP.NET works well, with itself. CF can interoperate with both Java and .NET tech, so no new code would have to be generated. CF can access .NET through a createObject() method for example.

Combined with the aforementioned smaller development time required to build a CF app, this makes CF a very useful solution for developing web applications.

For every case study for, their is a case study against. so the argument really is a moot point.

If you want a lot of learning pain, then do .Net.

If you want to get the job done, CF is just fine.

Cold Fusion is so much easier to do anything. I am taking a class in .NET right now and I can't believe all the work you have to do for the simplest things. CF gives a great advantage when the client is surprised how quickly we get things done. Use what you want, but CF is great for quick development which usually means very happy clients.

I'm converting 2 websites developed in the dot sh..tt! I started as asp developer but Microsoft doesn't respect it's technology, It has really a bad history against both the end user and developer. You can't depend or even respect a technology from theives of ideas. Let me give you example of what I mean: in 1996 Netscape navigator came with the idea of Cookies they stall it! Mozilla firefox came with the idea of Tags to browse as many sites without the need to carry on opening new windows... they made a resemblance! Microsoft immediately announced that they are not responsible of the previously FAT32 system when they launched the NTFS! They also killed VB script and asp for the dot sh..tt technology!

I really found macromedia the best and respect their products and clients... of course now macromedia belongs to adobe. Microsoft is trying to develop something to compete FLASH! they are really dreaming that Silverlight would do so! It would never!

I hate microsoft and would never respect them.

Adobe is the best among others.

OOP is not about reuse. People used to talk about reuse, but that's a dead claim. OOP's granularity is too large for handling real-world variations on concepts (and it gets ugly to shrink OO's granularity). Whatever OOP's other benefits may be, reuse is not a valid one. The real world often doesn't fit the textbook world of OOP claims of separation and reuse.