If I had to pick between the two, I'd actually toss out MVC. I've used both, and I've seen the results (and horror) of people doing the "Teach yourself ASP.NET

If I had to pick between the two, I'd actually toss out MVC. I've used both, and I've seen the results (and horror) of people doing the "Teach yourself ASP.NET in 21 days" version of ASP.NET, but really the stuff in those books isn't the stuff you should be using. ASP.NET done right actually feels a lot more MVC than ASP.NET MVC. You can still route whatever paths you want, but you get to use actual files where files make sense. And you get to sanely base your pages on a common class, and you can manipulate properties on your HTML from the backend. It's the best of both, really, since all the fun stuff from MVC got poured into ASP.NET too. I still do MVC work for clients, but as of now, new project stuff where I'm spending my own time (and therefore money) still gets done in regular old ASP.NET.