Campag you give the perfect world example. But if you go into any practical
application development with ASP.NET, you will find that databinding and
gridview/formview or whatever control you are using begins to lose its purpose.
So then you are forced to drag form elements and then coding the form/error
handling, then programmatically create a connection string in your web.config
file. Then you have do the code behind page, call the connections and actually
do something with the form variables, like insert or update. Then you get
something that looks and feels more familiar to asp classic. Don't forget you
postback to either hide the form variables and say thank you or redirect the
user to another page.
And Mister Compag how can you compare that to the cfform were everything can
be set like the default values, error handling, messages, etc. Then skipping
all the database crap (since it is registered with the server), and then
creating a simple cfif statement for the form submission response and
insert/update cfquery code.
You can't in 'real world' 'practical scenarios' say that ASP.NET is faster, or
better looking than CF. Unless you are a Microsoft paid operative here to
cause trouble...If that is the case, you should really spend your free time
helping the poor suckers on the asp.net forums figure out how to run their $300
copy of Visual Studio to over their new $150-$600 copy of Windows Vista.