This document provides an introduction and overview of ASP.NET Webforms and ASP.NET MVC. It discusses the key concepts of each including pages, page lifecycle, and controls for Webforms. For MVC, it outlines the model-view-controller pattern, routing, controllers and actions. It also compares the pros and cons of each approach and provides references for further reading.

1. Who I am
Emad Alashi
TTL in eSense Software
www.DotNetArabi.com
www.EmadAshi.com
Twitter: @EmadAshi

3. Introduction to

4. ASP.NET Webforms
• It’s all about Pages
• Request pages (*.aspx)
• Page lifecycle
• Control within the page
• Postback & Viewstate
• Tree of controls

5. Webforms Pros
 Rich Controls (grids, etc…)
 RAD
 Event Driven (Winforms)
 Statefull

6. Webforms Cons
 Less Control
 No built-in SoC
 Complicated Page life-cycle
 Not SEO friendly
 URL
 Big Viewstate at the beginning of the page

7. ASP.NET
MVC

8. MVC the pattern
Controller
ModelView

9. ASP.NET MVC

10. ASP.NET MVC
Pipeline:
 Routing
 Controller
 Action
 View
 High Flexibility

11. Code

12. View Engines
 Webforms view engine
 Bellevue
 Brail
 NDjango
 NHaml
 NVelocity
 Razor (favored by Microsoft recently)
 Spark

13. Razor
Webforms
Razor

14. Razor
Webforms
Razor

15. Spark
<ul if="products.Any()">
<li each="var p in products">${p.Name}</li>
</ul>
<else>
<p>No products available</p> </else>

16. Filters
 IAuthorizationFilter
 IActionFilter
 OnActionExecuting
 OnActionExecuted
 IResultFilter
 OnResultExecuting
 OnResultExecuted
 IExceptionFilter

17. Built on top of ASP.NET
platform
 Session Management
 Memebership
 Authentication & Authorization
 Caching
 Routing
 Configuration
 Global.asax
 Master files
 etc…

18. ASP.NET MVC Pros
 More control
 SoC
 SEO friendly
 TDD
 Flexible & customizable

19. ASP.NET MVC Cons
 Not RAD
 No rich controls

20. Important
• ASP.NET MVC is web in different taste
• Not replacing Webforms
• Not better

21. RESTful (by Roy Fielding)
 It’s all about nouns (Resources)
 A representation of a resource is typically a document
that captures the current or intended state of a
resource.
 URI
 Stateless
 Utilizes web architecture (Methods: GET, POST,
PUT, and DELETE)
 Simple
 Less bandwidth
 Generality
 Human readable

22. References
 www.asp.net/mvc
 Comparing Web Forms And ASP.NET MVC (Dino Esposito)
 Scott Guthrie: http://weblogs.asp.net/scottgu
 Scott Hanselman: www.computerzen.com
 Wikipedia: MVC, RESTful
 “Pro ASP.NET MVC 2 Framework” book by Steven
Sanderson
 ASP.net MVC Vs ASP.net Web Form
 REST vs. SOAP – The Right WebService
 REST (Representational State Transfer) and RESTful web
services: Methods, Concepts and Examples

23. Q & A
Emad Alashi
www.emadashi.com
www.dotnetarabi.com
@EmadAshi