>Along these lines, have you seen the new Razor stuff? That has to be the worst idea in a long time. I was so happy to see all of that awful in-line code and html switching go away from the ASP era and be replaced with code behind. Now they are acting like code behind is a bad word. All that in-line stuff makes for some of the worst opportunity for spaghetti code that I have ever seen.
>

Inline coding hadn't gone away in ASP.NET - you still embed code via the <% and %*gt; markers. This is even more true in ASP.NET MVC - while their is a clear distinction between code and view in MVC you're more likely to want to embed things like looping to build up your HTML. In those cases the Razor engine lets you do that but with less code. They're not promoting the idea that you stuff all your business logic back in the HTML like classic ASP, just trying to give you a way of writing more succinct code (that is specific to the view) when you do. They're also trying to enable the ability for developers to easily plug-in and use alternative view engines if they'd like (Spark, HAML, etc.)