Downloaded 67 times
Uploaded bykgpainter
Moving from ASP.NET Web Forms to ASP.NET MVC
This document discusses the differences between ASP.NET Web Forms and ASP.NET MVC frameworks. It notes that Web Forms provides a rich control-based programming model while MVC is based on the model-view-controller pattern, separating concerns. It also mentions that many companies have existing investments in Web Forms that they are unwilling to replace, and not all practice test-driven development that MVC encourages. The document considers options for converting an existing Web Forms application to MVC or running them side-by-side.
More Related Content
Similar to Moving from ASP.NET Web Forms to ASP.NET MVC
Moving from ASP.NET Web Forms to ASP.NET MVC
- 1.
- 3. Provides: Familiar control and event based programming model Rich controls that encapsulate HTML, CSS & Javascript Availability of many rich controls Browser differences handled for you SharePoint builds on Web Forms
- 4. The MVC patternwas invented in the '70s as part of Smalltalk. MVC divides your UI into three distinct objects: the controller, which receives and handles input; the model, which contains your domain logic; and the view, which generates your output.
- 5. Provides: A "separation of concerns” Significant control over rendered HTML Supports Unit Testing, TDD and Agile methodologies Encourages the use of design patterns by convention Encourages more prescriptive applications Extremely flexible and extensible
- 6.
- 7.
- 8.
- 10. “Many companies havea huge investment in Web Forms technology that they just simply aren't going to throw out - training, third party controls, experience and so on. “ “Many companies don't buy into the whole Unit Test pitch behind MVC. Many companies simply don't test at all.” Quotes from Mike Brind http://mikesdotnetting.com/
- 12. Quotes from ScottGuthrie’s blog on About Technical Debates (and ASP.NET Web Forms and ASP.NET MVC debates in particular)
- 13. Authentication Authorization User Membership Role Security OutputCaching Session State Configuration Deployment Ajax others...
- 14. Conversion Project Side-By-Side –Preexisting Web Forms app Side-By-Side – New MVC app
- 15.
- 16.
- 17. Why? Keeping rich functionalityof some desired server controls – such as the Report Viewer http://weblogs.asp.net/rajbk/archive/2010/05/11/running-asp-net-webforms-and- asp-net-mvc-side-by-side.aspx
- 18. Root.master <%@ Master Inherits="System.Web.UI.MasterPage"… %> MVC.master <%@ Master MasterPageFile="~/Views/Shared/Root.Master" Inherits="System.Web.Mvc.ViewMasterPage" … %> WebForm.master <%@ Master MasterPageFile="~/Views/Shared/Root.Master" Inherits="NorthwindSales.Views.Shared.Webform" %> Code behind: public partial class Webform : System.Web.UI.MasterPage {}
- 20. So back tothe question… Is it really worth moving from ASP.NET WebForms to ASP.NET MVC? It depends
- 21. Comparison Sites: http://coderjournal.com/2008/12/introducing-aspnet-mvc-part-2-aspnet-mvc-vs-webforms/ http://blog.gadodia.net/choosing-between-webforms-and-mvc/ http://msdn.microsoft.com/en-us/magazine/dd942833.aspx http://www.asp.net/web-forms/videos/how-do-i/choosing-the-right-programming-model Converting from Web Forms to MVC: http://codingatilivedigitally.wordpress.com/2012/07/10/9-steps-to-switch-from-asp-net-web-forms-to-mvc/ http://www.asp.net http://aspdotnetmvc.com/ ASP.NET MVC in Action (1-4) Programming Microsoft ASP.NET MVC Programming Microsoft ASP.NET 4