Asp.net mvc 5 course

1. ASP.NET MVC 5
COURSE
MODULE 1 : OVERVIEW
BY SERGEY SELETSKY

2. Course overview
 Module 1 : Overview
 Module 2 : Models
 Module 3 : Controllers
 Module 4 : Views
 Module 5 : Security
 Module 6 : Routing
 Module 7 : Performance
 Module 8 : Testing and Debugging
 Module 9 : Web API
 Module 10 : Integration

3. Agenda
 Introduction
 Architecture
 MVC vs Web Forms
 Project structure
 Configuration
 App show case
 Best practices
 Home work

4. Introduction
ASP.NET MVC framework is a lightweight,
highly testable presentation framework
that is integrated with existing ASP.NET features.
First version released at 13 March 2009
In April 2009, the ASP.NET MVC source code was released

5. Introduction
ASP.NET MVC enables a clean separation of concerns and that
gives you full control over markup.
TDD-friendly
Support latest web standards
RESTful by default

6. Architecture
ASP.NET Overview

7. Architecture
Controller
Retrieves Model
“Does Stuff”
View
Visually represents
the model
Model

8. MVC vs Web Forms
MVC Web Forms
Strengths
 Full control over HTML
 Clean HTML
 Separation of Concerns
 TDD-friendly
 Many View Engines
 RESTful by default
 Lightweight
 Simple integration
 Designed for RAD
 Visual Studio Designer
 Many third-party controls
 Easy for Win Forms engineers

9. MVC vs Web Forms
MVC Web Forms
Weaknesses
 Not based on server events
 Complex for Web Forms Dev's
 Few third-party libraries
 No View State
 UI linked with logic
 Difficult to test
 Large page size
 View State

10. MVC vs Web Forms
MVC Web Forms
Opportunities
 Allows to use TDD
 Reusable
 Better integrability
 RAD

11. MVC vs Web Forms
MVC Web Forms
Threats
 Difficult to learn
 Slow in developing
 Difficult to integrate
 Difficult for UI Developers

12. Project structure
By default, MVC projects include the following folders:
•App_Data, store folder for data. This folder has the same role in ASP.NET Web Forms.
•Content, which is the recommended location for static files.
•Controllers, which is the recommended location for controllers.
•Models, which is provided for classes that represent the app.
•Scripts, folder for script files.
•Views, which is the recommended location for views.

13. Project structure
Creating first project demo

14. Configuration
Routing configuration
public class RouteConfig
{
public static void RegisterRoutes(RouteCollection routes)
{
routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
routes.MapRoute(
name: "Default",
url: "{controller}/{action}/{id}",
defaults: new {
controller = "Home",
action = "Index",
id = UrlParameter.Optional }
);
}
}

15. Configuration
Bundling and Minifying configuration
public static void RegisterBundles(BundleCollection bundles)
{
bundles.Add(new ScriptBundle("~/bundles/bootstrap")
.Include("~/Scripts/bootstrap.js",
"~/Scripts/respond.js"));
bundles.Add(new StyleBundle("~/Content/css")
.Include("~/Content/bootstrap.css",
"~/Content/site.css"));
}
@Scripts.Render("~/bundles/bootstrap")
@Styles.Render("~/Content/css")

16. Real app showcase
Commercial open source app demo

17. Best practices
Keep Controllers Thin

18. Home work
Create your own solution
1. Create ASP.NET MVC 5 Project for future sessions
2. Create book model with few properties
3. Create view for book model
4. Create books controller
5. Use your book model in books controller
6. Implement creating and editing for books

19. References
Professional
ASP.NET MVC 5
By Jon Galloway
Pro ASP.NET MVC 5
By Adam Freeman
Programming
Microsoft ASP.NET
MVC, Third Edition
By Dino Esposito

20. THANK YOU
20
Sergey Seletsky
sselet@softserveinc.com
https://www.linkedin.com/in/sergeyseletsky