There has quite been the ASP.NET vs. MVC debates going on the internet these days. I must admit, I'm amused by it because it really comes down to personal preference, and what you are comfortable with. Most importantly, it should be dependent on what's best for the project at the moment. However, I do have one fear of what may be coming...
A while back, an open source initiative, Web Client Software Factory (http://www.codeplex.com/websf) was deployed as a viable option for creating applications using a composite development approach. This was something similar to the MVC framework: a better object-oriented approach to what web forms gave you. But since MVC came out, WCSF was last deployed Feb 28th, 2008. And so MVC is the new platform to develop applications in this manner, and I'm thanking God I didn't attempt to build an application using a framework no longer being updated.
A similar thing is happening with LINQ to SQL; it's going away (it's still around, but it's solely being maintained so what good is it if you don't get any enhancements). LINQ to SQL was created to get people into LINQ, only to tell them that you waisted your time because ADO.NET Entity Framework (not available at the time, and not released until many months later) was the future. if you invested in LINQ to SQL, it would still work, but you don't get the cool enhancements, updates, and new development, and there isn't a migration tool that I know of.
Is this ASP.NET's future? A good product to get people into .NET, but is no longer an important piece in application development? Time will tell. I actually have been reading about the MVC framework and do look forward to using it. Don't take this as a "I'm against MVC" posting; I am not. I just hope that those who invested millions of dollars into ASP.NET web forms will suddenly be looking at using a maintained product with no future. I certainly hope that isn't the case.