Asp.Net Webforms Vs Asp.Net WebSite(Razor) Vs Asp.Net MVC

Well, You have two options:\n\n\nUse WebForms: use out-of-the box, ready to use server-side controls(mixed markup and business codes) and use master pages and skins, but face some complexity involved of these conveniences! :)\nUse MVC: or use separated design model which gives you a more organized codebase. you can first make a design prototype, or first making a business codes, then building the other aspect, quite easy. even you can give the designer more control on his work, giving him/her the ability to do everything he/she wants.\n-> this one is my preferred choice because it gives me more control on my code, makes my code more concise and clean.\n\n\nIf you selected the MVC pattern, then you are faced with another options... View Engines\n\n\nOld MVC View Engine: it is not bad, but is a bit verbose\nRazor Engine: it does the same thing the #1 does, why you ever don't want to use it?! it replaces nothing of the MVC pattern. it is also more concise and easy, you have both the power of MVC and the simplicity of the Razor Engine. Razor is a smarter in-markup syntax, which helps you stay focused on your business, rather than writing \"<%\"s !\nby using razor syntax you are provided just a benefit, the full power of MVC is at your fingertips!\n\n\nYou can also write simple asp.net web pages just with razor(C# or VB) syntax. (just like php)\n\n\nMy personal choice would be MVC+Razor, The best combination!\n",

\nThere are no \"code-behinds\" in MVC, period. What you have are controllers, which exist both for Razor and non-Razor.\nThey're just two different types of markup. (See next answer)\nIt's not replacing MVC, it's just another option. The traditional markup is very verbose. Razor syntax is succinct. \n",

This is a great question. First, lets characterize Razor. \n\nRazor is an engine that parses server-side code an emits Html, just like ASP.NET Web Forms only with different and arguably more streamlined and terse syntax. \n\nRazor v. Web Forms Sidebar: In ASP.NET Web Forms you have to identify when you wanted to start writing server code with '<%' and then when you were done writing server code you needed to identify that with '%>'. I love ASP.NET Web Forms, but that's clunky. With Razor you identify when you want to start writing server code with '@' and then the next time you start writing a server tag (starting with '<') it \"figures out\" that you're done with server code. It's a more concise way to write html intermingled with some server code. \n\nASP.NET Web Pages is a framework for creating simple Web Applications. ASP.NET MVC is a framework for creating web applications with either the Web Forms or Razor engine using the Model-View-Controller (MVC) pattern. ASP.NET Web Forms is a framework for creating web applications using the Web Forms render engine. \n\nUltimately the goal is to provide choice based on the sophistication of the application that is being built. Understanding each with assist you in making the correct choice for your application.\n\nAdditional Links:\n\n\nScottGu's Blog - Introducing Razor\nScottGu's Blog - Introducing WebMatrix\nASP.NET Web Page with Razor Syntax (MSDN)\n",

In the MVC pattern, M is the Model, C is the Controller, and V is the View. So, quite naturally, in the ASP.NET MVC model, there is the concept of a View Engine. Razor is simply one of the View Engines provided. The other one provided out-of-the-box is the \"old\" WebForms one (you can also write your own View Engine by the way). So Razor does not have the notion of code-behind which stays within the WebForms view engine boundaries.\n\nSo this kinda says it all. Razor handles the View part of MVC (If you choose to use it instead of the WebForms one). It has nothing to do with M or C.\n\nPersonally, I would definitely go for the Razor View Engine if you choose the ASP.NET MVC pattern, or use plain WebForms without MVC, as Razor has been designed to be less verbose, more simple to use than the Webforms one. It's also simply more recent so it tries to be ... simply better :-)\n\nAs a side note, the Razor Parser can also be used outside of ASP.NET MVC. It's implemented in an assembly that does not rely on MVC nor Web assemblies at all. See here for more on this: http://www.west-wind.com/weblog/posts/2010/Dec/27/Hosting-the-Razor-Engine-for-Templating-in-NonWeb-Applications",

There are not code-behinds by default, but you can easily make your razor file inherits from your custom class:\n\n@inherits Index\n\n\nand then\n\npublic class Index : WebViewPage { }\n\n\n(More information here: http://www.compiledthoughts.com/2011/01/aspnet-mvc3-creating-razor-view-engine.html)\n\nThis is more like an old-fashioned way of doing web, more asp3-like. The difference with mvc is that mvc provides a huge framework that supports real world applications (using routing, controller and actions, and not just \"code there in the markup\").\n\nI think it exists for making things that are really simple, but I don't actually know...\n\nFinally, I would always chose asp.net mvc with razor.\n\nHope it helps",