ASP.NET MVC 3 (Adding a Controller) (2/9)

文章目錄

• Adding a Controller

Adding a Controller

MVC stands for model-view-controller. MVC is a pattern for developing applications such that each part has a separate responsibility:

• Model: The data for 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 to the client.

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

Create a new controller by right-clicking the Controllers folder in Solution Explorer and then selecting Add Controller.

Name your new controller "HelloWorldController" and click Add.

Notice in Solution Explorer on the right that a new file has been created for you named HelloWorldController.cs and that the file is open in the IDE.

Inside the new public class HelloWorldController block, create two new methods that look like the following code. We'll return a string of HTML directly from the controller as an example.

using System.Web.Mvc;  namespace MvcMovie.Controllers {     public class HelloWorldController : Controller     {         public string Index()         {             return "This is my <b>default</b> action...";         }          public string Welcome()         {             return "This is the Welcome action method...";         }             } }

Your controller is named HelloWorldController and your new method is named Index. Run the application (press F5 or Ctrl+F5). Once your browser has started up, append "HelloWorld" to the path in the address bar. (On my computer, it's http://localhost:43246/HelloWorld) Your browser will look like the screenshot below. In the method above, the code returned a string directly. We told the system to just return 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 invoked:

/[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 browse to /HelloWorld and the Index method was used by default. This is because a method named Index is the default method that will be called on a controller if one is not explicitly specified.

Browse to http://localhost:xxxx/HelloWorld/Welcome. The Welcome method runs and returns the string "This is the Welcome action method...". The default MVC mapping is /[Controller]/[ActionName]/[Parameters]. For this URL, the controller is HelloWorld and Welcome is the action method. We haven't used the [Parameters] part of the URL yet.

Let's modify the example slightly so that we can pass some parameter information from the URL to the controller (for example, /HelloWorld/Welcome?name=Scott&numtimes=4). Change your Welcome method to include two parameters as shown below. Note that we've used the C# optional-parameter feature to indicate that the numTimes parameter should default to 1 if no value is passed for that parameter.

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

Run your application and browse to http://localhost:xxxx/HelloWorld/Welcome?name=Scott&numtimes=4. You can try different values for name and numtimes. The system automatically maps 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 the VC portion of MVC — that is, the view and controller work. The controller is returning HTML directly. Ordinarily we don't want controllers returning HTML directly, since that becomes very cumbersome to code. Instead we'll typically use a separate view template file to help generate the HTML response. Let's look next at how we can do this.