Difference between ASP.NET Web App and ASP.NET MVC 3 Empty Web App?

I want to build my own web framework, and I want to build it in C#. I figure the easiest way to get started is to use ASP.NET to handle all the server communication stuff. The rest I want to build my self. I know next to nothing about ASP.NET. (But know C#, the MVC pattern, and other web frameworks quite well).

In Visual Studio 2010 I see

• ASP.NET Web Application
• ASP.NET MVC 2 Empty Web Application
• ASP.NET MVC 3 Empty Web Application

I figure one of these should be good as a base. I just want some "entry point" into some C# code开发者_如何学编程. I started with PHP so it's a little bit weird for me to not be able to just load up a file in my browser. Anyway, which should I use? What's the difference between a plain ASP.NET Web App and an empty MVC 3 app? If it's "empty" it shouldn't be using any of the MVC framework, should it? I just want to make sure I use the latest and greatest "ASP" for handling the server stuff before I embark down this road.

Perhaps you shouldn't start with an Empty Web Application, because it just gives you the references to the assemblies, but doesn't give you any sample code.

ASP.NET Web App, is a NOT empty web app (meaning it has a basic setup of files), meant to be used with ASP.NET WebForms. For tutorials: http://www.asp.net/web-forms

ASP.NET MVC 2 Empty Web Application is an empty project, meant to be used with ASP.NET MVC version 2 (the current version). For tutorials: http://www.asp.net/mvc

ASP.NET MVC 3 Empty Web Application is an empty project, meant to be used with ASP.NET MVC version 3 (now a release candidate). For info: http://www.asp.net/mvc/mvc3

Before creating your framework, dig into the tutorials, play around, and only then start building your framework.

And about WebForms vs MVC, that's a whole other discussion. I personally switched for my new project to MVC, and perhaps it's better suitable for your Framework app.