I agree with Ben Forta, there is no apples to apples comparison. If you are integrating with Office (excel, word, or outlook automation) or COM objects, I would use .NET. .NET has a lot of advantages on the windows platform. However, saying that CF is better because you can run it on multiple platforms does not hold water because PHP runs on more platforms than either one. Also, I have converted a few sites from Linux to windows and windows to Linux (and UNIX), it has never been smooth.
I use CF if I can get away with it. .NET is not just a development platform, but it is a whole new way of doing web development. Therefore learning for existing programmers is tough, you have to forget your normal CGI patterns of programming that you have become used to over the last 12 years. Server site form elements confused me at first, it seemed like a stupid way to do it, but I got used to it. Just like I got used to tag based coding (That seemed stupid to me at first also) when moving from EXE's and ASP to CF 7 years ago. It's just another web development language meant to confuse us and waste our time arguing and training. A lot of us forget: The right tool for the right job. Jacob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Woodward Sent: Thursday, June 09, 2005 8:45 AM To: [email protected] Subject: Re: CF VS .Net? Probably the best resource for this discussion is here: http://forta.com/blog/index.cfm?mode=e&entry=1266 Sean Corfield from Macromedia also recently had a blog post in which he mentioned that they built the same app in both C# and CF and CF took somewhere on the order of 1/4 the development time--I'll try and dig that up. There was also a very long thread several months ago on the Macromedia forums about this (mostly perpetrated by yours truly) but I can't dig it up in their search. Some of the high points as I remember them were these: * more flexibility for deployment with CF (server OS, J2EE, .NET with BlueDragon, etc.) * faster development times with CF typically * more out-of-the-box features with CF (graphing, reporting, Verity), although .NET does have some nice front-end controls The ONLY con really is that CF 'isn't free,' but of course with .NET you have to pay for Windows and the application has to live on Windows the rest of its life. Also even on moderate-sized projects, the CF license cost pays for itself with all the extras you don't have to buy and the savings in development time. That should be enough to get the ball rolling. ;-) Matt On Jun 9, 2005, at 6:56 AM, David Whatley 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 > > > -- Matthew Woodward [EMAIL PROTECTED] ---------------------------------------------------------- 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
