• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
ZZ BC#7 asp.net mvc practice and guideline by NineMvp
 

ZZ BC#7 asp.net mvc practice and guideline by NineMvp

on

  • 1,633 views

 

Statistics

Views

Total Views
1,633
Views on SlideShare
1,633
Embed Views
0

Actions

Likes
4
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    ZZ BC#7 asp.net mvc practice and guideline by NineMvp ZZ BC#7 asp.net mvc practice and guideline by NineMvp Presentation Transcript

    • ASP.NET MVCPractice and GuidelineZubzib Black Coffee #7
    • About me • Chalermpon Areepong (Nine) • Microsoft MVP ASP.NET • Work @
    • Session Level 300Audience Skill• HTML• JavaScript• C#• OOP• LINQ
    • Agenda• Basic ASP.NET MVC Programming o Model o View o Controller o Routes• NuGet Package Manager• Entity Framework 4.x Code First Introduce• Application Layer Architecture• Repository Pattern• Dependency Injection
    • Basic of ASP.NET MVCPrograming• Model : o Class Model, Domain Transfer Object (DTO), View Model o Model Validation • Validation Attribute, IValidationObject Interface• View : User Interface o Engine : ASPX ViewEngine, Razor ViewEngine, Etc…… o HTML, CSS, JavaScript• Controller o Control logic, o Data access, o Prepare parameters for view render o call view to render output
    • Basic of ASP.NET MVCPrograming• DEMO
    • Basic of ASP.NET MVC Programing• Routes o Catch URL to parameter by pattern • Default “{controller}/{action}/{id}” http://www.zz.com/blog/get/1 • Fix route value new { controller = “blog”, action = “get”, id = 1 } • Custom Routes o blog/Archive/12-25-2009 “{controller}/{action}/{date}” http://www.zz.com/blog/Archive/12-25-2009 Public ActionResult Archive(DateTime date) o blog/Archive/12-25-2009_12-17-2011 “{controller}/{action}/{dateFrom}_{dateTo}” http://www.zz.com/blog/Archive/12-25-2009_12-17-2011 public ActionResult Archive(DateTime dateFrom, DateTime DateTo)
    • Basic of ASP.NET MVC Programing• Routes DEMO
    • NuGet Package Manager• Library Utility for o Search o Install / Update / Uninstall o Execute library command (PowerShell)• VS - > Menu -> Tools -> Extension Manager -> Find NuGet and install• How to use o Project Reference o Package Manager Console • Install-Package <package name> • Uninstall-Package <package name> • Get-Package
    • NuGet Package Manager• DEMO
    • EF 4.x Code First• Object Relational Mapping• POCO• Convention Over Configuration• LINQ Support• Working with various database (3rd party driver)• Fluent API to fully customize the persistence mapping• Demo…..
    • EF 4.x Code First• DEMO
    • MVC UI LibraryAll will render to HTML/ CSS / JavaScript• JQuery UI• Telerik MVC Extension (current not full support HTML5)• Knockout (MVVM)• Kendo UI (HTML5)• Wijmo (HTML5)
    • MVC UI Library• DEMO
    • Software Design:Repository Pattern• Encapsulate data access• Simple collection like interface• Should only return aggregate roots• Provide for adding and removing entities• Provide methods to select objects based on some criteria• Allow easy substitution
    • Software Design:Repository Pattern• DEMO
    • Software Design:Core Layer ArchitectureMotivation – Logical layers separate the majorconcerns of the application:• 1. Modularity, low-coupling – easier maintenance.• 2. Business-logic is separated from presentation – reuse.• 3. General technical services, e.g., database, are separated from the business-logic – reused, replaced.• 4. Low coupling, separation of concerns – evolving functionality, system scaling-up, adapt to new technologies.
    • Software Design:Core Layer Architecture
    • Software Design:Core Layer Architecture• DEMO
    • Dependency Injection• Dependency Injection - one example of IoC design principle.• Also known as the Hollywood Principle o Don’t call us, we’ll call you!• Good OO Systems – organised as web of interacting objects• Goal – High cohesion, low coupling• Advantages of low coupling o Extensibility o Testability o ReusabilityPS>Not so easy to achieve!
    • Dependency Injection• Demo
    • Summary• ASP.NET MVC• NuGet• EF Code First• JavaScript Framework• AutoFac MVC Integration• Bye…