Hi Jeff,
I just have a few comments-
Extendibility for ASP.NET does not have to be a COM object. Server
controls can be written in any .NET-supported language or as COM object.
Server controls can take the form of HTML-like tags that can written
inline like HTML or instantiated as an object in the code-behind and
added dynamically to the page. The code controlling the page can also
control either form of the server control.
Error handling - I think that ASP.NET does have a default error handling
mechanism that is enabled through the WEB.CONFIG file. I'm not really
familiar with it but I'm pretty sure it is there and not too hard to set
up. Trapping errors in script is as straightforward (IMHO) as in CF - I
don't know why you think it is limiting.
Web-server Support - There is an organization that is working on a .NET
version for Linux (I think UNIX also) but I can't remember the name of
it. I'm not sure if this counts on your list, though.
Web services are easy in ASP.NET but probably not as easy as in CFMX.
Web forms in ASP.NET are truly a forward leap from conventional Web
programming. It's very similar to writing an event-driven windows
application. You should really try writing a webform and see how easy
it is, how many things you don't have to think about because of the
persistence of the form elements and the presentation code that you
write only once. It's a new paradigm and not necessarily suited for
every situation, but it's truly great in the right situations.
I know it sounds like I am really sticking up for ASP.NET (and I do in
some situations) but in this case I just want to try to present the
truth for your comparison page. I don't correct any CFMX stuff because
I don't know it as well. Also, this is a situation where you know CFMX
better than ASP.NET and therefore aren't making mistakes with CFMX.
- Matt Small
-----Original Message-----
From: Jeffry Houser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 8:53 PM
To: CF-Community
Subject: CFMX vs ASP.NET
Hi All,
I just caught up on Candace's thread on choosing CF or .NET.
Ironically, I just threw this together this morning, which is a
comparison of CF to
.NET. <http://www.instantcoldfusion.com/resources/cfmxasp.cfm> .
Comments would be welcome, specially from people w/ .NET experience.
Based on my experience, I bet the difference between CF and .NET on
large
scale projects (I.E. 6 months or more) would be negligible (Assuming all
other things being equal). I spend more time setting up the data
connection than I would with CF, but once I get that, there are more
options for dealing with that database data. I think it all evens out.
--
Jeffry Houser | <mailto:[EMAIL PROTECTED]>
AIM: Reboog711 | Phone: 1-203-379-0773
--
My Books: <http://www.instantcoldfusion.com>
--
We Provide The Soundtrack to your Web: <http://www.fcfstudios.com>
--
Original Energetic Acoustic Rock: <http://www.farcryfly.com>
We need one hundred fifty thousand dollars to promote our next CD
I'll take a check
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=5
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=5
Host with the leader in ColdFusion hosting.
Voted #1 ColdFusion host by CF Developers.
Offering shared and dedicated hosting options.
www.cfxhosting.com/default.cfm?redirect=10481
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
