Презентация на тему ASP.NET MVC 5. Part 1. Overview. Controllers. Views

It receives and handles user queries, interrupts with Model,

and returns results by View objects
Model – contains classes that represent data, performs operations with data-bases and organizes relations between data-classes.
View – performs UI representation. Works with model.

Development
Cross platforms support
Windows, PDA, IPhone, …
HTML code control
Clear ULR

navigation
http://musica.ua/groups/metallica
Maintainable code and command work

MvcScaffold integration
HTML 5 enabled project templates
The Razor View Engine
Support

for Multiple View Engines
Controller Improvements
JavaScript and Ajax
Model Validation Improvements
Dependency Injection Improvements

to Default Project Templates
Mobile Project Template and Empty Project

Template
jQuery Mobile, the View Switcher, and Browser Overriding
Task Support for Asynchronous Controllers
Azure SDK
Database Migrations
Add Controller to any project folder
Bundling and Minification
Enabling Logins from Facebook and Other Sites Using OAuth and OpenID

template
ASP.NET Identity
Bootstrap
Authentication filters
Filter overrides
Attribute routing

Features in ASP.NET MVC 5.1
Attribute routing improvements
Bootstrap support for

editor templates
Enum support in views
Unobtrusive validation for MinLength/MaxLength Attributes
Supporting the ‘this’ context in Unobtrusive Ajax
New Features in ASP.NET MVC 5.2
Attribute routing improvements

it's more typical to pass in parameters as route

data than passing them as query strings

";" or any other characters you want as part

of your route rules
This would pass appropriate "language", "locale", and "category" parameters to a ProductsController:
{language}-{locale}/products/browse/{category}
/en-us/products/browse/food
language=en, locale=us, category=food
You can use the "." file extension type at the end of a URL to determine whether to render back the result in either a XML or HTML format
products/browse/{category}.{format}
/products/browse/food.xml category=food, format=xml
/products/browse/food.html category=food, format=html

properties the Razor view has, including:
AjaxHelper (through the Ajax

property)
HtmlHelper (through the Html property)
ViewData and model
UrlHelper (through the Url property)
TempData and ViewContext
To specify a layout inside a view, we can specify the layout to use with the Layout property:

@{
Layout = "~/Views/Shared/_Layout.cshtml";
}

view engine
is responsible for rendering views in the

Razor format (either .cshtml files or .vbhtml files)
The Web Form view engine is used to support the older-format Web Form views (.aspx and .ascx files)

Web Forms view engine example:
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage" %>

<% foreach(var product in Model) { %>

• <%: product.Name %>

<% } %>

Razor view engine example
@model Product[]

@foreach(var product in Model) {

• @product.Name

}

magic character that precedes code instructions in the following

contexts
‘@’ For a single code line/values


‘@{ … }’ For code blocks with multiple lines



‘@:’ For single plain text to be rendered in the page

Current time is: @DateTime.Now

@{
var name = “John”;
var nameMessage = "Hello, my name is " + name + " Smith";
}

@{
@:The day is: @DateTime.Now.DayOfWeek. It is a great day!
}

can be included at any part of the code:




Razor

uses code syntax to infer indent:

@if(IsPost){

Hello, the time is @DateTime.Now and this
page is a postback!

} else {

Hello, today is:

@DateTime.Now
}

// This won’t work in Razor. Content has to be // wrapped between { }
if( i < 1 ) int myVar=0;

ways to pass data to a view:
by using the

ViewDataDictionary,
by using the ViewBag,
by using strongly typed views.

perform type casts whenever you want to retrieve something

from the dictionary.

a way to pass data from the controller to

the view
It makes use of the dynamic language features of C# 4
Set properties on the dynamic ViewBag property within your controller:
A ViewBag property is also available in the view:

by default:
System.Web.Mvc.WebViewPage or
System.Web.Mvc.WebViewPage
Class WebViewPage provides a strongly typed wrapper

over ViewData.Model through the Model property and provides access to strongly typed versions of the associated view helper objects - AjaxHelper and HtmlHelper

type using the @model keyword, view will inherit from

WebViewPage instead of WebViewPage, and we will have a strongly typed view

public ActionResult Index()
{
//…
SomeModel model = new SomeModel();
return View(model);
}

Name:

@Model.Name

Date Added:

@Model.DateAdded

Message:

@Model.Message

you find yourself copying and pasting one snippet of

HTML from one view to the next, that snippet is a great candidate for a partial
To render a partial we can use the RenderPartial method or the Partial method in a parent view

the partial markup in the locations:
\\.cshtml
\Shared\.cshtml
\\.cshtml
\Shared\.cshtml
In order to prevent

accidentally using a partial view from an action, we prefix the view name with an underscore
Html.RenderPartial(...) renders the partial immediately to the response stream
Html.Partial(...) returns a string
In Razor, Html.RenderPartial must be in a code block