Man,
When asp.net came out, a new term was born, “code behind”. This pattern promises “separation of UI and logic code”.
My ASS!!!
The more I work with asp.net web forms pattern, the more I become frustrated with the code-behind model. There IS no separation. Once you put an ID and runat=”server” attribute on a UI element, you have NOW BOUND that element to any code in the “separated” code-behind.
I’m gonna write more on this soon. But for now, I’m leaning more and more to the NVelocity pattern for UI.
Reading Materials:
http://weblogs.asp.net/asmith/archive/2004/04/14/112916.aspx
May 10, 2011 @ 08:21:34
Scott,
You really summed it up in you short blog. Seperation My Ass! Viva La Architecture Design Patterns such as MVC, etc.