Do-it-yourself Cheat Sheet

This section contains the step-by-step solutions to the do-it-yourself exercises. You normally shouldn’t need it if you follow the book in order. But I know you have only a week to learn ASP.NET MVC and I don’t want you to remain stuck in any exercise. So here are the steps.

",{"_237":238,"_43":44,"_47":48,"_45":46,"_65":66,"_239":240,"_279":235},"previewContent","

\n Introduction\n
- \n What this book is not\n
- \n Prerequisites\n
- \n How to read this book\n
- \n Tools you need\n
- \n Source code\n
\n
\n 1. What is ASP.NET MVC and why use it\n
- \n 1.1 What is it ?\n
- \n 1.2 Why use it ?\n
- \n 1.3 Competing technologies\n
\n
\n 2. Creating our Web Site\n
\n 3. ASP.NET MVC inner workings\n
- \n 3.1 Principles\n
- \n 3.2 View\n
\n
\n 4. Create an application and modify the home page\n
- \n 4.1 Do-it-yourself 1 - Create the application\n
- \n 4.2 Do-it-yourself 2 - Change the home page\n
\n
\n 5. Razor\n
\n 6. Understanding ASP.NET MVC\n
\n 7. Typing things up\n
\n 8. Updating server data\n
- \n 8.1 Action parameters\n
- \n 8.2 Word of caution about URLs\n
- \n 8.3 Do-it-yourself 8 - Display product details\n
- \n 8.4 HTTP Post parameters\n
- \n 8.5 Passing a full blown object\n
- \n 8.6 Sit and watch - Basic product calculator\n
- \n 8.7 Do-it-yourself 9 - Add a search box to the products list\n
\n
\n 9. Updating data scenario\n
- \n 9.1 Steps\n
- \n 9.2 Controller\n
- \n 9.3 Automated generation of controller and views\n
- \n 9.4 Do-it-yourself 10 - Create the products management back-office\n
\n
\n 10. Doing more with controllers and actions\n
\n 11. Basic security\n
\n 12. Going further\n
\n Do-it-yourself Cheat Sheet\n
\n Definitions\n

Introduction

\n\n

What this book is not

\n\n

I made my best to keep this book small, so that you can learn ASP.NET MVC quickly without getting lost in petty details. If you’re looking for a reference book where you’ll find answers to all the questions you may have within the next 4 years of your ASP.NET MVC practice, you’ll find other heavy books for that.

\n\n

My purpose is to swiftly provide you with the tools you need to code your first ASP.NET MVC application and be able to look for more by yourself when needed. While some authors seems to pride themselves in having the thickest book, in this series I’m glad I achieved the thinnest possible book for my purpose. Though I tried my best to keep all of what seems necessary, based on my 14 years experience of teaching .NET.

\n\n

I assume that you know what ASP.NET MVC is and when to use it. In case you don’t, read the following What is ASP.MVC chapter.

\n\n

Prerequisites

\n\n

In order for this book to meet its goals, you must :

\n\n

Have basic experience creating applications with .NET and C#
Have working knowledge of HTML
Know what a Web application is

\n\n

How to read this book

\n\n

This book’s aim is to make you productive as quickly as possible. For this we’ll use some theory, several demonstrations, plus exercises. Exercises appear like the following:

\n\n\n\n

Tools you need

\n\n

The only tool you’ll need to work through that book is Visual Studio 2015. You can get any of those editions:

\n\n

Visual Studio 2015 Community (free)
Visual Studio 2015 Professional

\n\n

Source code

\n\n

All of the source code for the demos and do-it-yourself solutions is available at https://bitbucket.org/epobb/aspnetmvc

\n\n

It can be downloaded as a ZIP file, or if you installed GIT you can simply type:

\n\n

git clone https://bitbucket.org/epobb/aspnetmvc.git\n

\n\n\n\n\n

\n1. What is ASP.NET MVC and why use it

\n\n

This book assumes that you (or your boss) decided to use ASP.NET MVC knowing what it is. In case you do, you can safely\nignore this chapter. But if you don’t, read this chapter before reading the book and you’ll be good to go.

\n\n

\n1.1 What is it ?

\n\n

In a nutshell, ASP.NET MVC is a technology used to create Web applications.

\n\n

Web applications are used with a browser. Example of Web applications are Facebook, Google, and in fact most of the services you use.\nWhen you enter an http://something url in your browser, you get a Web application.

\n\n

Simply put, ASP.NET MVC can be used to create a Web application like Facebook. Or a store, which is what we do in this book’s exercises.

\n\n

\n1.2 Why use it ?

\n\n

In case you know .NET and need to create a Web application, using ASP.NET makes sense since you can reuse your knowledge of the .NET Framework (or .NET Core) and language abilities (like C# and VB.NET).

\n\n

There are several technologies inside of ASP.NET you may consider:

\n\n

ASP.NET Web Forms: good for creating small and large Web applications when you know almost nothing to HTTP and HTML, but have experience developing client applications (for instance Windows Forms or WPF).
ASP.NET Web Pages: good for creating small Web applications without bothering with the structure.
ASP.NET MVC: good for creating large Web applications when you know HTTP and HTML.
ASP.NET Web API: good for creating REST APIs.

\n\n

Though you can mix all of those technologies in a single ASP.NET Web application, choosing just one is a reasonable choice. Mixing several technologies would be done when you need to maintain for instance ASP.NET Web Forms but want to add new features using ASP.NET MVC.

\n\n

\n1.3 Competing technologies

\n\n

There are many technology stacks used to create Web applications. On a technological standpoint the following stacks would for instance allow to develop applications in a way similar to ASP.NET MVC :

\n\n

Node.JS + Express
Ruby on Rails
Meteor

\n\n

Selecting one technology or another can be debated for a while. It often boils down to beliefs or preferences, be there can be good reasons. For instance, if you know JavaScript and HTTP but nothing about .NET, you’ll probably get an easier time with Node.JS + Express than with ASP.NET MVC.

\n\n

\n2. Creating our Web Site

\n\n

Here’s how we create an ASP.NET MVC Application.

\n\n

Remember: you watch and memorize this, don’t try to do it now. Please bear with me, I promise you’ll get fun a bit later.

\n\n

Let’s start Visual Studio 2015 and select File / New / Project from the menu. I know New Web Site sounds tempting but don’t use it, that kind of site doesn’t scale up well once you get to real applications.

\n\n

I’m taken to the New project dialog box:

\n\n\n

\n\n\n

From the left menu I’ll select Visual C# since it’s the most common coding language for .NET, then Web. In the middle pane I’ll select ASP.NET Web Application and in the right pane I’ll ensure the Add application Insights to Project is unselected (because I don’t need them). In the lower part of the dialog box I’ll type the name of my project: Demos.

\n\n\n

\n\n\n

Now I click the OK button and I’m taken to a second dialog: New ASP.NET Project. Time to select the features we want. I’ll select MVC and keep the other default options as shown on that screenshot:

\n\n\n

\n\n\n\n\n

Now I click the OK button of the New ASP.NET Project dialog. I’m taken to a Configure Microsoft Azure Web App dialog. This is for my application’s later hosting on the Web. I’ll just click the Cancel button since I want to configure that later – or never in case I deploy my application elsewhere.

\n\n

That’s it for now: my application is ready. In order to run it inside my browser, I’ll select Debug / Start Debugging from the menu, or use the F5 shortcut:

\n\n\n

\n\n\n

When I do this, Visual Studio starts a local Web server (IIS Express), runs my browser and points it to the URL of my site on that server, and finally attaches to the running code in debug mode so that it can catch any exception or show the code when I read a breakpoint.

\n\n

This is what I get in my browser:

\n\n\n

\n\n\n

What’s nice is that the site is responsive (the default template uses Boostrap):

\n\n\n

\n\n\n

That application also has a menu above, with links that take me to almost empty “About” and “Contact” pages. Also note that we already have fully-functional “Log in” and “Register” links for user authentication. If I use them, a local SQL Server database will be created and used for storage.

\n\n

Well, we have kind of a nice startup after just a few clicks. Now let’s see some theory before we can extend our application. Don’t worry, I’ll keep it short: this book focuses on getting you up and running quickly.

\n\n

\n3. ASP.NET MVC inner workings

\n\n

\n3.1 Principles

\n\n

When our browser queries an ASP.NET MVC URL, there are three elements that work together in order to produce an HTML page:

\n\n

A View produces the HTML;
A Controller:\n
- fetches the data and provides it to the view
- selects the view
\n
A Route selects the controller.

\n\n

That’s an easy process. Here’s a schema of it:

\n\n\n

\n\n\n

\n3.2 View

\n\n

Once inferred from the URL, the view is looked for into the following paths:

\n\n

Views/[Controller]/[Action].aspx
Views/[Controller]/[Action].cshtml
Views/Shared

\n\n

When coding the view, you can choose between one of two syntaxes (or add another one):

\n\n

ASPX
Razor

\n\n

We’ll use Razor since it’s a concise view language crafted specifically for ASP.NET MVC. ASPX is a syntax that will sound familiar to those coming from ASP.NET Web Forms.

\n\n

Before we begin learning about the Razor syntax, we’re going to have a look at what’s part of the Visual Studio template that was created.

\n\n

Let’s take a look at the project structure. For this I’ll use the Solution Explorer.

\n\n\n

\n\n\n

You can see that there is a “Views” folder containing a “Home” sub-folder, inside of which there is an “Index.cshtml” file. As seen above, when ASP.NET looks for the view corresponding to the “Index” action of the “Home” controller, it will get that Views\\Home\\Index.cshtml file. Sound abrupt? Bear with me.

\n\n

Let’s open the Views\\Home\\Index.cshtml file. Apart for the first 3 lines, it contains pure HTML markup. That’s the markup that will be rendered to the browser. And it is also Razor code.

\n\n

So you just learned a secret: Razor code is basically HTML code. In fact, it’s HTML in which we’ll add some special statements using the @ mark. Yeah, I know you’re beginning to love ASP.NET MVC, or at least Razor.

\n\n

Inside the solution, we can also find a Controllers\\HomeController.cs file:

\n\n\n

\n\n\n

Let’s open that file.

\n\n

public class HomeController : Controller\n{\n    public ActionResult Index()\n    {\n        return View();\n    }\n\n    // ...\n}\n

\n\n\n\n

You can see that the class is named HomeController, and it contains a public method named Index. When ASP.NET looks for the view corresponding to the “Index” action of the “Home” controller, it will get this method.

\n\n

The “Index” method contains a simple return View(); statement. It means that the default view should be returned for that action.

\n\n

We’re almost there. Now let’s have a look at the App_Start\\RouteConfig.cs file. It contains the following code:

\n\n

routes.MapRoute(\n    name: \"Default\",\n    url: \"{controller}/{action}/{id}\",\n    defaults: new { controller = \"Home\", action = \"In\\\ndex\", id = UrlParameter.Optional }\n);\n

\n\n\n\n

This is the routing configuration. See the url property? It states how ASP.NET MVC will parse incoming URLs. As of now this is the only line, but you may add as many as you wish here.

\n\n

What url: \"{controller}/{action}/{id}\" means is that if someone types the http://mysite/home/index URL in their browser ASP.NET will invoke the Index action from the Home controller. It also states that if someone types the http://mysite URL in their browser ASP.NET will invoke the Index action from the Home controller because they are the defaults.

\n\n

Got it? Now let’s sum up what happens for a sample request:

\n\n

Someone types http://mysite/home/index in their browser.
ASP.NET MVC understands it has to look for the Index action from the Home controller, so it invokes the Index method from the HomeControllerclass.
The return View(); statement means the ASP.NET needs to return the default view.
ASP.NET fetches the Views\\Home\\Index.cshtml file and renders it to the browser. It’s HTML which can be enhanced using the Razor syntax.

\n\n

Easy, isn’t it? Well that’s almost all there is to ASP.NET MVC. Read those four steps again until you get them right, because they are the backbone of the ASP.NET process.

\n\n

Time to put in practice all of that stuff you just learned. And I bet your fingers are itchy for coding.

\n\n

\n4. Create an application and modify the home page

\n\n

Do-it-yourself time! You should do the following two exercises. If having a hard time, you can look at the detailed steps in the do-it-yourself cheat sheet at the end of this book, but I’m sure you won’t need it.

\n\n

\n4.1 Do-it-yourself 1 - Create the application

\n\n\n\n

\n4.2 Do-it-yourself 2 - Change the home page

\n\n\n\n

\n5. Razor

\n\n\n\n

\n6. Understanding ASP.NET MVC

\n\n\n\n

\n7. Typing things up

\n\n\n\n

\n8. Updating server data

\n\n

\n8.1 Action parameters

\n\n

When updating server data, you need to pass information from the browser to your application. This is simply handled by the routing system which will call your actions with parameters.

\n\n

Let’s look again at the default route in the Global.asax file

\n\n

RouteTable.Routes.MapRoute(..., \"{controller}/{action\\\n}/{id}\",\n    new { \"...\", id=UrlParameter.Optional} );\n

\n\n\n\n

Note the {id} part? It means that anything coming after the action name (and separated from it by a slash sign) will be considered as an id parameter. And that this parameter is optional.

\n\n

In order to get this parameter, all you have to do is add a parameter with the same name to you action method. For instance :

\n\n

public class ProductsController : Controller\n{\n  public ActionResult Action1(string id)\n  { ... }\n}\n

\n\n\n\n

Considering the default route, this action can be called simply by typing the following URL :

\n\n

http://site/products/action1/abcd\n

\n\n\n\n

In that case, our ProductsController.Action1 method will be invoked with a value of abcd for its id parameter.

\n\n

We could add as many parameters as needed to our action and modify the route accordingly. Needless to say that parameters should be short, since they add up to the URL length.

\n\n\n\n

Whatever happens, we can also pass action parameters using query parameters. Consider for instance the following action :

\n\n

public class ProductsController : Controller\n{\n  public ActionResult Rename(int id, string newName)\n  { ... }\n}\n

\n\n\n\n

In order to invoke it with an id value of 15 and a newName value of sandwich, we can simply use the following URL

\n\n

http://site/products/rename/15?name=sandwich\n

\n\n\n\n

Note that sandwich is passed as a query parameter since it’s not part of the route definition. We could also modify the route definition - or add a new one - in order to make it part of the URL.

\n\n

\n8.2 Word of caution about URLs

\n\n

As we saw earlier, route definitions may change later, for instance in order to improve SEO or provide user-friendly URLs. Which means it’s important not to rely on them in your views.

\n\n

The following view code will break if the route change, so avoid using it :

\n\n

@* bad *@\n<a href=\"/home/index/3\">Some page</a>\n

\n\n\n\n

Instead, you should prefer :

\n\n

@* good *@\n@Html.ActionLink(\"Some page\", \"Index\", \"Home\", new { \\\nid=3 }, null)\n

\n\n\n\n

or even :

\n\n

@* good *@\n<a href=\"@Url.Action(\"Index\", \"Home\", new { id=3 })\">\\\nSome page</a> \n

\n\n\n\n

\n8.3 Do-it-yourself 8 - Display product details

\n\n\n\n

\n8.4 HTTP Post parameters

\n\n

Providing action parameters through the URLs is adapted for short parameters that can appear to the user. In case you want to pass longer action parameters or hide them from the URL, you can pass them as form data. It’s almost as simple.

\n\n

The view should declare a form in order to have the parameters sent :

\n\n

<form method=\"post\">\n    First Name: <input name=\"firstname\" type=\"text\" />\n    <input type=\"submit\" />\n</form>\n

\n\n\n\n\n\n

In order to get the parameter, all that our view needs to to is declare a parameter with the same name :

\n\n

public class ProductsController : Controller\n{\n  [HttpPost]\n  public ActionResult Action1(string firstname)\n  { ... }\n}\n

\n\n\n\n

Note the [HttpPost] attribute attached to the action method. By default, an action only reacts to HTTP GET requests, that’s why we need it for a HTTP POST.

\n\n

Now, if you don’t want ASP.NET MVC to generate part of your form, you can use an HTML helper. Our view above would become

\n\n

@using (Html.BeginForm())\n{\n    <input name=\"firstname\" type=\"text\" />\n    <input type=\"submit\" />\n}\n

\n\n\n\n

The same would go for the HTML input field and submit.

\n\n

\n8.5 Passing a full blown object

\n\n

ASP.NET MVC can make your job easy when you need to update full objects. Let’s suppose you created a Person class :

\n\n

public class Person\n{\n    public string FirstName { get; set; }\n    public string LastName { get; set; }\n}\n

\n\n\n\n

You can write an action that takes a Person object as a parameter

\n\n

public class PersonController : Controller\n{\n  [HttpPost]\n  public ActionResult CreatePerson(Person p)\n  { ... }\n}\n

\n\n\n\n

All you need to do is to make sure that the incoming HTTP request contains parameters whose names match the properties declared in the Person class. ASP.NET will create a Person instance and pass it to your action.

\n\n

For instance, we could write the following matching view :

\n\n

@using (Html.BeginForm(\"CreatePerson\", \"Person\"))\n{\n    <input name=\"firstname\" type=\"text\" />\n    <input name=\"lastname\" type=\"text\" />\n    <input type=\"submit\" />\n}\n

\n\n\n\n

\n8.6 Sit and watch - Basic product calculator

\n\n

Let’s begin with a simple example. I want to create a page that allows users to compute the product of two numbers. Easy. I’ll first write a ViewModel class :

\n\n

public class ComputeProductViewModel\n{\n    public ComputeProductViewModel(decimal? number1, \\\ndecimal? number2)\n    {\n        Number1 = number1 ?? 0;\n        Number2 = number2 ?? 0;\n        Result = Number1 * Number2;\n    }\n\n    public decimal Number1 { get; private set; }\n    public decimal Number2 { get; private set; }\n    public decimal Result { get; set; }\n}\n

\n\n\n\n

As seen earlier, a ViewModel can have properties for everything that is input by and output to the user.

\n\n\n\n

I’ll then add a ComputeProduct action method to my Home controller. Note that it takes two parameters: the numbers to multiply :

\n\n

public class HomeController : Controller\n{\n    public ActionResult ComputeProduct(decimal? numbe\\\nr1, decimal? number2)\n    {\n        var viewModel = new ComputeProductViewModel(n\\\number1, number2);\n        return View(viewModel);\n    }\n}\n

\n\n\n\n

Now I’ll right-click the ComputeProduct method and select Add View... from the contextual menu, then select an Empty template and my ViewModel as a model for my view :

\n\n\n

\n\n\n

As my view code I’ll type :

\n\n

@model Demos.ViewModels.Home.ComputeProductViewModel\n\n<h2>Product of two numbers</h2>\n\n@using (Html.BeginForm())\n{\n    @Html.TextBoxFor(m => m.Number1)\n    @Html.TextBoxFor(m => m.Number2)\n    <input type=\"submit\" value=\"Compute\" />\n}\n\n<label>Result: @Html.DisplayFor(m=>m.Result)</label>\n

\n\n\n\n

Not much new here, except for the use of two HTML helpers

\n\n

Html.TextBoxFor generates an input field for a given model member
Html.Diplay generates a display element for a given model member

\n\n

Both come in very handy since they take a lambda expression that provides your model and expects the member for with to generate the HTML element. Since we have a typed model thanks to the @model directive, it’s plain easy to type thanks to IntelliSense and C# type-inference. Try it in your own Visual Studio and you’ll be surprised how streamlined the experience is.

\n\n

Let’s run our view (Debug / Start Without Debugging menu). We get the following result in our browser :

\n\n\n

\n\n\n

Of course, if works. When we input some numbers and click the Compute button, we get our result :

\n\n\n

\n\n\n

It works. No surprise. Just one more thing: remember we can provide action parameters using URL query parameters? It works here too. If we call our calculator view using the following URL :

\n\n

http://localhost:58599/Home/ComputeProduct?number1=5.\\\n2&number2=8\n

\n\n\n\n

…we get the following result without event clicking the Compute button (notice the URL) :

\n\n\n

\n\n\n\n\n\n\n

\n9. Updating data scenario

\n\n

\n9.1 Steps

\n\n

Now we need to support data input in a real-world scenario, not just sending some partial data. When you input data in a Web application, you do so through an HTML form. In fact, that process can be broken in two steps, whatever the server-side technology

\n\n\n

\n\n\n

\n9.2 Controller

\n\n

Those two steps mean rendering a view twice, once for HTTP GET and once for HTTP POST. Which in turn means two actions on our controller. Your controller would typically look like :

\n\n

public class ProductsController : Controller\n{\n  public ActionResult Edit(int id)\n  {\n    ... // fetch data from data source\n  }\n\n  [HttpPost]\n  public ActionResult Edit(int id, Product p)\n  {\n    ... // update the data source\n  }\n}\n

\n\n\n\n

When the data source update is successful, you probably don’t want the user to remain on the data input form. Which means the POST action would most likely contain a redirect statement. There is a RedirectToAction method for this on the base Controller class. It comes in handy since we provide the name of the action we want to redirect to :

\n\n

[HttpPost]\npublic ActionResult Edit(int id, Product p)\n{\n  // ...\n  if(successful) {\n    return RedirectToAction(\"Index\");\n  }\n}\n

\n\n\n\n

\n9.3 Automated generation of controller and views

\n\n

Now is time for me to show you a gem. In case we use Entity Framework as a data access layer, Visual Studio can generate in a breeze the controller, actions and views needed for a full CRUD scenario. What’s more, the generated code isn’t scary and can be modified to fit your needs.

\n\n

Let’s see how it works. Remember we have the following model that we wrote a while ago :

\n\n

public class Car\n{\n    public int ID { get; set; }\n    public string Model { get; set; }\n    public double MaxSpeed { get; set; }\n}\npublic class GarageFactory : DbContext\n{\n    public DbSet<Car> Cars { get; set; }\n    // ...\n}\n

\n\n\n\n

All I have to do is right-click the Controllers directory in Solution Explorer and select Add / Controller... from the contextual menu :

\n\n\n

\n\n\n

In the Add Scaffold dialog box I select “MVC 5 Controller with views, using Entity Framework” and click the Add button :

\n\n\n

\n\n\n

That gets me another dialog box, Add Controller, which I’ll fill in the following way :

\n\n

Model class: Car\n
Data context class: GarageFactory\n
Generate views: checked (default value)

\n\n

I’ll leave the rest of the options to their default values. Here’s the dialog box before I press the Add button :

\n\n\n

\n\n\n

That’s all there is to it! I now have full actions and views for each CRUD operation.

\n\n

Let’s go for instance to the list of cars. We type the http://localhost:58599/Cars URL in our browser and get a nice list :

\n\n\n

\n\n\n

What’s more, there are links to create, edit, delete and details views, all working. Time to get the paycheck and go surfing for the next week.

\n\n\n\n

Well, I can feel that your fingers are getting itchy again. You want to try this by yourself? Great, that’s just what we’re about to do!

\n\n

\n9.4 Do-it-yourself 10 - Create the products management back-office

\n\n\n\n

\n10. Doing more with controllers and actions

\n\n\n\n

\n11. Basic security

\n\n\n\n

\n12. Going further

\n\n\n\n\n

Do-it-yourself Cheat Sheet

\n\n

\n\n\n\n

Definitions

\n\n\n\n\n

\n\n","tocStructure",[241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274,275,276,277,278],{"_76":77,"_43":78,"_70":-5,"_79":80,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":86,"_70":-5,"_79":87,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":92,"_70":-5,"_79":93,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":95,"_70":-5,"_79":96,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":98,"_70":-5,"_79":99,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":101,"_70":-5,"_79":102,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":104,"_70":-5,"_79":105,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":108,"_70":-5,"_79":109,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":111,"_70":-5,"_79":112,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":114,"_70":-5,"_79":115,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":117,"_70":-5,"_79":118,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":121,"_70":-5,"_79":122,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":125,"_70":-5,"_79":126,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":128,"_70":-5,"_79":129,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":131,"_70":-5,"_79":132,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":135,"_70":-5,"_79":136,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":138,"_70":-5,"_79":139,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":141,"_70":-5,"_79":142,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":145,"_70":-5,"_79":146,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":149,"_70":-5,"_79":150,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":153,"_70":-5,"_79":154,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":157,"_70":-5,"_79":158,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":160,"_70":-5,"_79":161,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":163,"_70":-5,"_79":164,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":166,"_70":-5,"_79":167,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":169,"_70":-5,"_79":170,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":172,"_70":-5,"_79":173,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":175,"_70":-5,"_79":176,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":178,"_70":-5,"_79":179,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":182,"_70":-5,"_79":183,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":185,"_70":-5,"_79":186,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":188,"_70":-5,"_79":189,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":85,"_43":191,"_70":-5,"_79":192,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":194,"_70":-5,"_79":195,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":198,"_70":-5,"_79":199,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":202,"_70":-5,"_79":203,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":206,"_70":-5,"_79":207,"_72":81,"_88":-5,"_89":-5,"_90":-5},{"_76":77,"_43":210,"_70":-5,"_79":211,"_72":81,"_88":-5,"_89":-5,"_90":-5},"publicChapterContent","nextChapter","sections",[],"routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Do-it-yourself Cheat Sheet

Table of Contents

Introduction

What this book is not

Prerequisites

How to read this book

Tools you need

Source code

\n1. What is ASP.NET MVC and why use it

\n1.1 What is it ?

\n1.2 Why use it ?

\n1.3 Competing technologies

\n2. Creating our Web Site

\n3. ASP.NET MVC inner workings

\n3.1 Principles

\n3.2 View

\n4. Create an application and modify the home page

\n4.1 Do-it-yourself 1 - Create the application

\n4.2 Do-it-yourself 2 - Change the home page

\n5. Razor

\n6. Understanding ASP.NET MVC

\n7. Typing things up

\n8. Updating server data

\n8.1 Action parameters

\n8.2 Word of caution about URLs

\n8.3 Do-it-yourself 8 - Display product details

\n8.4 HTTP Post parameters

\n8.5 Passing a full blown object

\n8.6 Sit and watch - Basic product calculator

\n8.7 Do-it-yourself 9 - Add a search box to the products list

\n9. Updating data scenario

\n9.1 Steps

\n9.2 Controller

\n9.3 Automated generation of controller and views

\n9.4 Do-it-yourself 10 - Create the products management back-office

\n10. Doing more with controllers and actions

\n11. Basic security

\n12. Going further

Do-it-yourself Cheat Sheet

Definitions