I just somebody's got to be the defender. Here are a few things that I have
direct experience using:
"reading/writing a file is generally done through a file stream object,
not easy to comprehend, and more code than <cffile>."
Declare the file to write to and write.
Dim FSO As FileStream = File.OpenWrite("file.txt")
FSO.Write("Content")
"uploading a file... haven't done it, sounds difficult."
ImageUploadField.PostedFile.SaveAs("Image.jpg");
"cfdump? they do have debugging, but not a "dump your vars" quickie
shortcut."
<%@ trace="true" %>
"For consuming a web service, you have to create a stub, usually through
the command-line tool wsdl.exe, or through VS.NET (see: web reference).
Then call the local stub object just like you would a local class. It's
not really more code, it's just more work, which is why Ben said it was
"difficult"."
Overall I find it as easy to use as anything else in .NET, simply because
it's treated exactly the same as regular code.
I will say that you're going to be faster writing CF. I think that writing
code in ASP.NET is going to be less bug-prone because of the heavy reliance
on the OOP paradigm. So it's really a matter of time saved now vs.
long-range maintenance.
It will take you longer to learn ASP.NET, but that's not necessarily a bad
thing. Experience in any field is worth more than book learning.
Matthew Small
Web Developer
American City Business Journals
704-973-1045
[EMAIL PROTECTED]
-----Original Message-----
From: Nathan Strutz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 5:21 PM
To: CF-Talk
Subject: Re: Not to start a flame war.....
Ian Skinner wrote:
> <quote>
> (cfhttp, cffile, cfftp, flash forms, cfchart, cfdump, cfreport,
cfdocument, flash remoting, omg, where to stop? ).
> </quote>
>
> Is it fair and unbiased to say that it is easier to do these things in
ColdFusion then ASP.NET?
>
Yep.
reading/writing a file is generally done through a file stream object,
not easy to comprehend, and more code than <cffile>.
uploading a file... haven't done it, sounds difficult.
Http request aren't so bad. A generic get or simple post isn't too hard
to do. If you start getting into complex stuff, you may find yourself
overriding half the system.net objects.
ftp? I think you have to manage the sockets and sent ftp commands
manually. I havn't had experience.
flash forms? yeah right.
flash remoting? only through a product from macromedia.
cfchart, cfdocument, cfreport? only through 3rd party tools or a LOT of
coding on your part.
cfdump? they do have debugging, but not a "dump your vars" quickie shortcut.
For consuming a web service, you have to create a stub, usually through
the command-line tool wsdl.exe, or through VS.NET (see: web reference).
Then call the local stub object just like you would a local class. It's
not really more code, it's just more work, which is why Ben said it was
"difficult".
-nathan strutz
http://www.dopefly.com/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble
Ticket application
http://www.houseoffusion.com/banners/view.cfm?bannerid=48
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211848
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
