> Dave, I'd have to disagree with you here. ASP.NET's > code-behind is sweet feature. Yes, it helps desktop > developers transition but the things you can do in a > code-behind are VERY nice, which CF can't do. > > For instance: > - The different steps of a page loading you have access over > (much more than App.cfc gives you) > - Controlling page elements (with runat="server") from the > code-behind at the different parts of the page loading > - 100% complete separation of code and visuals (no > instantiation of objects, etc at the top of the page...they > are already there)
You do know you can rewrite every HTML tag as a CF custom tag, right? You simply point CFIMPORT to a directory containing form.cfm, a.cfm, etc. That gets me <form runat="server"> if I want it. You could mimic enough of what ASP.NET does in code-behind, if you wanted to - I just don't see a compelling reason to do so. I don't dislike code-behind, I just don't see any value in trying to translate that model into CF. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262201 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
