As mentioned in previous episodes, my team is standardizing on the ASP.NET MVC Framework for web development. One thorn in our sides has been that by default, Visual Studio would create a code-behind for your views automatically, and if you wanted a view that used a strongly typed model, such as ViewPage<Person> or ViewPage<ProductCollection> then you
had to create a code-behind file.
There were CLR hacks to do this in the code in front, but they were just awful.
In webforms, code-behind made sense, in MVC not so much. I think they tend to encourage developers to write code in the old webforms way, and not use the controllers and helper methods as much. One of the reasons to move to MVC is to return to simplicity--no page events, no controls, no viewstate. Code-Behind is a blemish on that simplicity.
Well the nail has officially been driven into the coffin for our old friend code-behind. In the next version of MVC, it can go away completely:
http://weblogs.asp.net/scottgu/archive/2008/12/19/asp-net-mvc-design-gallery-and-upcoming-view-improvements-with-the-asp-net-mvc-release-candidate.aspxYou can still add code-behind if you are perverted, twisted, abomination of a developer, but its no longer there by default.
DIE Code-Behind! DIE!!!
(oh and normalize your fucking databases.)