I've done CF for about 5 years (1year of MX) and C# and Asp.net for 2years.  I've compiled a quick list of pros and cons for CF and .NET

 

CF. 
-pluses
----------------
Dev time (smaller projects)
Ease of writing queries (form and capture applications were very quick to write)
CFDUMP (saved my sanity.  .NET does not natively have hierachial debugging without VS.net)
Less platform dependent (eventhough I never deployed an app to a non windows system)
Often times less expensive to hire CF developer (good for employer)
Reporting and graphing (said in earlier post)
Verity (one of my favorites)
Flex (but it is expensive)
Flash remoting (alternatives like OpenLaslo (free) are clumsy)

-minuses
Often times less expensive to hire CF developer (Bad for developer)
CF's association with Dreamweaver gives the public perception that it is "a language for web designers, not programmers")

 .NET
-pluses
---------------
Dev sanity (larger projects)
Most larger companies are either doing .NET or J2EE (CF is often not considered real J2EE by the Java community, eventhough it is)
The code I write for web apps can often be taken out and put into a windows form
Encourages you to learn windows development. THIS IS HUGE (the transition from Asp.net to windows dev is very simple. I'm now able to develop many more solutions and consider myself as a Asp.net/Windows developoer  I could easily get a job doing asp.net or traditional windows dev)
Power of ADO.net (eventhough I don't interact with DB using LLBLGen (object persistance framework))
Perception that it is more difficult (it is at first)
Documentation (MSDN docs and the thousands of sites devoted to .net dev)
Developer community
Framework is "free" (if you buy windows) :)
.NET v2.0  (is awesome!!!)
3rd party products  (there are thousands)
Large framework (over 35000 objects.  Very robust.  Gives you the ability to do awesome things)
Tricky code like complex algorithms are easier to write
 -minuses
price of VS.net if you don't have a MSDN
Platform dependent (yeah, yeah MONO)
I'm working with devil
 
Lyndon

 
On 6/9/05, Jacob Cameron <[EMAIL PROTECTED]> wrote:
Have you priced RedHat Enterprise edition lately?  Last time I compared Microsoft, RedHat and Suse, they were all around the same price!!!
 
Jacob
 

From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Kent Irvin

Sent: Thursday, June 09, 2005 9:59 AM
To: [email protected]
Subject: Re: CF VS .Net?

 
ASP is not free, in runs on a proprietary web server which requires Windows Y2K or higher.   That is not a free sceneario in my mind.

Kent

Knipp, Eric wrote:
Tom,

Did you go back to Thomson?

Eric

-----Original Message-----
From: [EMAIL PROTECTED] [
mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 09, 2005 9:33 AM
To: [email protected]
Subject: RE: CF VS .Net?


I've started doing some C# programming and agree that it's a waste of
time to do C# without visual studio.  The good thing that I've seen
about C# and .net is that everything is an object.  The intelli-sense in
Visual Studio is awesome.  I would love to see Macromedia/Adobe add that
functionality to DreamWeaver.  It would be cool as you code to know what
methods and properties are available from your CFC.

ColdFusion is hands down easier to develop with IMO.  But that could be
a factor of what you are used to.  8 or 9 years of CF development versus
2 weeks of C#.  Hmmmmm.

The knock on CF is that it's not free like ASP or PHP.  Not sure of what
VisualStudio costs, but that has to be included in the comparison.

Tom

-----Original Message-----
From: [EMAIL PROTECTED] [
mailto:[EMAIL PROTECTED]] On
Behalf Of Matthew Woodward
Sent: Thursday, June 09, 2005 8:59 AM
To: [email protected]
Subject: Re: CF VS .Net?

I've done two smallish projects in C#, and if you don't use Visual  
Studio the amount of code you have to write is HEINOUS.  If you plan  
to do any amount of .NET development whatsoever, add Visual Studio  
licenses to the total cost because writing all that code by hand is a  
nightmare.  To me that's not a strength of the Visual Studio tool,  
it's a weakness of the language. ;-)  I just don't understand why  
everything other than CF (and some J2EE servers of course) doesn't  
manage your datasources so you can have simple query statements like  
we have in CF, and that's just one example.  All that extra code adds  
up quickly.

Matt

On Jun 9, 2005, at 8:49 AM, John Ivanoff wrote:

  
A while back ben forta blogged on this "Defending ColdFusion  
Against ASP.NETMailScanner has detected a possible fraud attempt from "www.forta.com" claiming to be 
MailScanner has detected a possible fraud attempt from "www.forta.com" claiming to be MailScanner has detected a possible fraud attempt from "www.forta.com" claiming to be "
http://www.forta.com/blog/index.cfm?mode=e&entry=1264

he said it should be more J2EE vs .NET
"ASP.NET apps take advantage of the .NET framework and infrastructure,
just like ColdFusion apps take advantage of J2EE"

I've looked into .NET and to me it's like programming cobol. 30* lines
of code to do a "HELLO WORLD" But I'm sure you can do some really cool
stuff with it.

* not really but sure seems like 30.

On 6/9/05, David Whatley <[EMAIL PROTECTED]> wrote:

    
Just for discussion, what are the pro's and cons on CF versus .Net?

David Whatley
COO
AutoRealty Products
817-284-9875 X 105



----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
   http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
   http://www.dfwcfug.org/form_MemberRegistration.cfm




      
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
   http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
   http://www.dfwcfug.org/form_MemberRegistration.cfm



    
  


Reply via email to