Adding a Controller

MVC stands for Model, View, Controller.

MVC is a pattern for developing applications such that each part has a responsibility that is different from another.

• Model: The data of your application
• Views: The template files your application will use to dynamically generate HTML responses.
• Controllers: Classes that handle incoming URL requests to the application, retrieve model data, and then specify view templates that render a response back to the client

We'll be covering all these concepts in this tutorial and show you how to use them to build an application.

Let's create a new controller by right-clicking the controllers folder in the solution Explorer and selecting Add Controller.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;

namespace Movies.Controllers
{
    public class HelloWorldController : Controller
    {
        public string Index()
        {
            return "This is my default action...";
        }

        public string Welcome()
        {
            return "This is the Welcome action method...";
        }  
    }
}

Your Controller is named HelloWorldController and your new Method is called Index.

Run your application again, just as before (click the play button or press F5 to do this).

Once your browser has started up, change the path in the address bar tohttp://localhost:xx/HelloWorld where xx is whatever number your computer has chosen.

Now your browser should look like the screenshot below.

In our method above we returned a string passed into a method called "Content."

We told the system just returns some HTML, and it did!

ASP.NET MVC invokes different Controller classes (and different Action methods within them) depending on the incoming URL.

The default mapping logic used by ASP.NET MVC uses a format like this to control what code is run:

/[Controller]/[ActionName]/[Parameters]

The first part of the URL determines the Controller class to execute.

So /HelloWorld maps to the HelloWorldController class.

The second part of the URL determines the Action method on the class to execute.

So /HelloWorld/Index would cause the Index() method of the HelloWorldcontroller class to execute.

Notice that we only had to visit /HelloWorld above and the method Index was implied.

This is because a method named “Index” is the default method that will be called on a controller if one is not explicitly specified.

Now, let's visit http://localhost:xx/HelloWorld/Welcome. 

Now our Welcome Method has executed and returned its HTML string.

Again, /[Controller]/[ActionName]/[Parameters] so Controller is HelloWorld and Welcome is the Method in this case.

We haven't done Parameters yet.

Let's modify our sample slightly so that we can pass some information in from the URL to our controller, for example like this: /HelloWorld/Welcome?name=Scott&numtimes=4.

Change your Welcome method to include two parameters and update it like below.

Note that we've used the C# optional parameter feature to indicate that the parameter numTimes should default to 1 if it's not passed in.

   public string Welcome(string name, int numTimes = 1)
        {
            string message = "Hello " + name + ", NumTimes is: " + numTimes;
            return "" + Server.HtmlEncode(message) + "";
        }

Run your application and visit http://localhost:xx/HelloWorld/Welcome?name=Scott&numtimes=4 changing the value of name and numtimes as you like.

The system automatically mapped the named parameters from your query string in the address bar to parameters in your method.

In both these examples the controller has been doing all the work, and has been returning HTML directly.

Ordinarily we don't want our Controllers returning HTML directly - since that ends up being very cumbersome to code.

Instead we'll typically use a separate View template file to help generate the HTML response.

Let's look at how we can do this.

Close your browser and return to the IDE.