> Using code-behind (asp.net class) and web forms (viewstate) are two of the > MAJOR advantages of using ASP.NET.
Code-behind is nice, but I've seen it become a pain in the arse with really big applications. You wind up with all this controller code spread through hundreds of pages / components, and when your model changes, you have to automagically remember which code behinds deal with that portion of the model, and go update them. I think I just have a personal preference for front controllers over page controllers. > It's a web analogy to a regular application And most "regular application"s are scary! A lot of VB apps I've seen are very anti-architecture (redneck voice: "Hey y'all, we'll just stick the logic on this here button's OnClick!"), and code-behind is now letting the same shlock spread to web apps. Struts, Rails, and, well, almost all of the other MVC frameworks make it nigh impossible to do this kind of crap, and ASP.NET all but encourages it. IMHO, ASP.NET is a great technical achievement that got blemished when MS's marketing group realized they could sell it as "VB for Web apps," perpetuating shitty implementations that'll keep hundreds of MCADs employed as maintenance programmers for decades. -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211849 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
