Adding a Controller (VB)
This tutorial will teach you the basics of building an ASP.NET MVC Web application using Microsoft Visual Web Developer 2010 Express Service Pack 1, which is a free version of Microsoft Visual Studio. Before you start, make sure you’ve installed the prerequisites listed below. You can install all of them by clicking the following link: Web Platform Installer. Alternatively, you can individually install the prerequisites using the following links:
- Visual Studio Web Developer Express SP1 prerequisites
- ASP.NET MVC 3 Tools Update
- SQL Server Compact 4.0(runtime + tools support)
If you’re using Visual Studio 2010 instead of Visual Web Developer 2010, install the prerequisites by clicking the following link: Visual Studio 2010 prerequisites.
A Visual Web Developer project with VB.NET source code is available to accompany this topic. Download the VB.NET version. If you prefer C#, switch to the C# version of this tutorial.
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.
[!code-vbMain]
1: Namespace MvcMovie
2: Public Class HelloWorldController
3: Inherits System.Web.Mvc.Controller
4:
5: Public Function Index() As String
6: Return "This is my default action..."
7: End Function
8:
9: Public Function Welcome() As String
10: Return "This is the Welcome action method..."
11: End Function
12:
13: End Class
14: End Namespace
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 visit /HelloWorld above 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 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 in 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 VB optional parameter feature to indicate that the numTimes parameter should default to 1 if no value is passed for that parameter.
[!code-vbMain]
1: Public Function Welcome(ByVal name As String, Optional ByVal numTimes As Integer = 1) As String
2: Dim message As String = "Hello " & name & ", NumTimes is: " & numTimes
3: Return "" & Server.HtmlEncode(message) & ""
4: End Function
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 at how we can do this.
)
| <SITEMAP> <MVC> <ASP> <NET> <DATA> <KIOSK> <FLEX> <SQL> <NOTES> <LINUX> <MONO> <FREEWARE> <DOCS> <ENG> <CHAT ME> <ABOUT ME> < THANKS ME> |