I've been playing around asp.net mvc just recently, i was really shocked and somewhat struggling with this new framework since i was used to the traditional N-Tier development with asp.net. As I developed simple examples, asp.net mvc is somewhat similar to n-tier development. As such, each layers have been separated to enable designers and coders to work independently with each layer. I have some books in my arsenal but i haven't read them yet.LOL Basically, I'm still a newbie with this stuff. One tip that i read was choosing between asp.net webforms and asp.net mvc. This will provide insights on other developers as well. Choosing between ASP.NET MVC and ASP.NET Webforms Source: ASP.NET MVC 1.0 Quickly In general, choosing between ASP.NET MVC and ASP.NET can be based on the following five criteria: 1. Are you considering test-driven development (TDD)? TDD enables you to write tests for an application first, after which the application logic is developed. An ASP.NET Webfor