We actively use asp.net "classic" as you have referred to it. It's an alternative and in by no means inferior to MVC. We are looking at implementing MVC3 but to

We actively use asp.net "classic" as you have referred to it. It's an alternative and in by no means inferior to MVC. We are looking at implementing MVC3 but to do what we do with asp.net webforms will be a difficult task. We wrote a CMS framework for our own clients and we use quite a lot of specific .net webforms controls to do what we do. The main reason I started moving away from silverlight and more into html and js, mvc etc was because of Windows 8 not having silverlight as part of the interface. This is exactly what I mean by Microsoft getting it's head out the sand though, they have chosen to use the more adopted methods going forward than it's own solutions. It's a sign that Microsoft are no longer at the center of the universe. I'm not putting down your comment on who in their right mind uses "classic" asp.net any more but I find it a little closed minded as asp.net webforms is far more tried and tested. It's a developers choice and it's not a wrong choice to use forms over mvc.