"Back in the day" of Betas 1 and 2 I would have definitely agreed with you. I was coming from VB/ASP and this databinding crap and databound control crap was great, as long as it was simple. The moment I needed to start having anything more complex (a databound control within a databound control that could optionall have a databound control) I quickly abandoned the new .NET way of doing things and went back to concatenating html strings, Response.Write()ing html, etc. However, like any other technology, it takes time to fully learn how to do things. I'm still learning now, however things that I thought were difficult, impossible, or implausable a year ago I look at now and wonder why I never thought of doing it the way I'm doing it now. I will definitely say that (business code aside, we're talking straight display now) I write each page at least four to five times faster than I used to. I have no complex loops in ASP that determine what to show and what not to show, I don't have to modularize my ASP into functions so I can reuse one tiny bit of ASP magic that display some data (so it can be used within complex loops and if statements). Now it's write the HTML, drag on some server controls, use panels for things that will show/hide (or just control visibility on each form), and DataBind.
adam.. > Here is $0.02 more for your pot. Having moved from a pure coding (ASP, >VB Script, etc) web background into a company that uses .NET and web forms >I can tell you that I found them to be a bit restrictive at first. Here >is my take for what it is worth. > Yes, the web forms are actually very useful if you simply want to display >your data in a linear format using the various controls provided by .NET >like DataGrids, DataLists, Repeaters, etc. Code behind pages still >provide you with a large amount of programatic control over how your pages >are processed, and with the ability to use C#, VB.Net, etc. you have a >much more powerful language base to work with than the traditional VB >Script/Java Script language base of ASP. However, it takes a bit more work >to get your pages to display exactly the way you want with web forms vs. >traditional ASP. If your page is more complicated than a "query and >display" page then you need to start working with nesting controls within >other controls and binding different tables, dataviews, etc. to the >controls to create more complex pages. It can get a bit frustrating >trying to find the right combination of nested controls and data binding >relationships to make your page display the way you want to. It these >situations I find myself longing to abandon the web forms and go back to >the traditional pure coding techniques of old. Hope this helps. --- You are currently subscribed to dotnet as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------- Administrated by 15 Seconds : http://www.15Seconds.com List Archives/Search : http://local.15Seconds.com/search Subscription Information : http://www.15seconds.com/listserv.htm Advertising Information: http://www.internet.com/mediakit/
