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
