ASP.NET MVC框架入门与实践

需积分: 10 195 浏览量更新于2024-07-29 收藏 4.81MB PDF 举报

"ASP.NET.MVC.in.Action.pdf" ASP.NET MVC 是一个用于构建动态Web应用程序的框架，由微软开发，提供了一种模型-视图-控制器（Model-View-Controller）的设计模式，使得开发者能够更清晰地分离业务逻辑、数据处理和用户界面。《ASP.NET MVC in Action》这本书深入介绍了这个框架的各个方面，旨在帮助读者掌握ASP.NET MVC的使用。在第一章"Getting started with the ASP.NET MVC Framework"中，作者介绍了开始使用ASP.NET MVC框架所需的基础知识，包括系统需求，如何运行起始项目，以及逐步进阶的"Hello, World"示例。这些基础示例旨在让读者快速上手并理解MVC的基本工作流程。此外，章节还涵盖了强类型视图的概念，这是一种能够确保视图与模型数据类型匹配的机制，从而提高代码的健壮性和可维护性。第二章"The Model in depth"详细讲解了模型层的实现，包括数据模型的设计、数据验证以及如何与数据库交互。模型是应用程序的核心，负责处理业务逻辑和数据管理。第三章"The Controller in depth"关注控制器，它是模型和视图之间的桥梁。控制器接收HTTP请求，处理业务逻辑，并决定如何响应，包括选择哪个视图来呈现结果。第四章"Views in depth"深入探讨视图的创建和使用，视图是用户看到和交互的部分，通常由HTML、CSS和JavaScript组成。书中可能包括如何使用Razor语法创建动态视图，以及如何与模型数据进行交互。第五章"Routing"讲述了ASP.NET MVC中的路由系统，这是决定URL如何映射到控制器动作的关键部分。通过自定义路由规则，开发者可以创建更加友好的和可定制的URL结构。第六章"Customizing and extending the ASP.NET MVC Framework"讨论了如何根据项目需求对框架进行扩展和定制，包括编写自定义过滤器、扩展视图引擎和控制器行为。第七章"Scaling the architecture to more complex sites"关注大型复杂网站的架构扩展，讨论如何处理性能优化、分层设计和模块化等问题。第八章"Leveraging existing ASP.NET features"讲解如何利用ASP.NET框架的其他功能，如身份验证、授权、缓存等，来增强ASP.NET MVC应用的功能。第九章"AJAX in ASP.NET MVC"探讨如何在MVC应用程序中集成异步JavaScript和XML技术，以提供更流畅的用户体验。第十章"Hosting and deployment"介绍部署ASP.NET MVC应用到生产环境的策略和注意事项，包括IIS配置、调试和性能监控。第十一章"Exploring Mono Rail and Ruby on Rails"可能对比分析了ASP.NET MVC与其他Web开发框架，如基于Ruby的Rails，以拓宽视野。第十二章"Best practices"提供了关于编码、测试和项目管理的最佳实践，帮助开发者遵循行业标准，提升代码质量。第十三章"Recipes"则是一些解决常见问题的实战方案，为开发者提供了快速解决问题的参考。这本书全面覆盖了ASP.NET MVC框架的各个方面，无论你是初学者还是经验丰富的开发者，都能从中获益，提升在ASP.NET MVC上的技能和知识。

}

Notice that the public

Index

action method is all that is necessary for this controller to be web-callable.

Simple content action methods need not return

ActionResult

. Returning any other type will result in that object

being rendered as content to the response stream.

If we point our browser to

/HelloWorld2, we'll see that our controller sends exactly the same response to the

browser as shown in figure 1.7 Now that we know how to craft a controller, we will explore our first view.

Figure 1.7 Notice the web page has the same output as before. The end result is the same even though the controller

implementation has evolved.

1.3 Our First View

Recall that the ASP.NET MVC Framework uses a convention for locating views. The convention is to find an .aspx

file in a directory tree that matches /Views/controllername/actionname.aspx. In our next example, we will modify

our controller a bit by calling a method on the

Controller

base class called

View()

. We'll set the model, which

is a

string

with the text, "Hello World", to an entry in the

ViewDataDictionary

object on the

ViewData

property of the

Controller

base class. This

ViewDataDictionary

instance will be forwarded to the view.

Although ViewData is a ViewDataDictionary we recommend you only depend on the IDictionary<object, object>

interface if you are replacing the view engine. View engines will be discussed in more detail in chapter 4. Below,

in our example, we see that our action returns ActionResult instead of void. After an action method returns, the

ActionResult executes to perform the appropriate behavior, which is rendering a view in this case. Examine listing

1.9 for the current implementation of our controller.

ViewData

contains the object that will be forwarded on to

the view. The

View()

method also supports passing a single object to the view that is then accessible via

ViewData.Model

, which we will explore later.

Listing 1.9 Using a view to render the model.

using System.Web.Mvc;

namespace MvcApplication.Controllers

{

public class HelloWorld3Controller : Controller

{

public ActionResult Index()

{

//Adding objects to view data allows the framework

//to pass them to the view

ViewData.Add("text", "Hello World3");

return View();

}

Listing 1.10 A simple view. Note how we extract the object passed from the controller from the ViewData

dictionary.

<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage" %>

<%--/Views/HelloWorld3/Index.aspx --%>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

</head>

<body>

<div>

</div>

</body>

</html>

The flow from our controller to or view is very, very simple. The controller designates one or many objects to

be forwarded to the view and then declares the name of the view. The MVC Framework will locate the view,

instantiate it, push in the ViewData, and have the view render itself to the response stream. The

ViewPage

base

class fully supports rendering, but ViewState, postbacks, and the server-side post-back events no longer happen.

Rendering events still fire, however since ViewPage derives from

System.Web.UI.Page

. The view’s responsibility

is to transform objects passed to it into HTML. This is a very key part of the Separation of Concerns that Microsoft

is focusing on for this product. The controller does not know how the view is doing the formatting. The only point

of coupling is that the controller names the view. It does not matter that the

System.Web.Mvc.WebFormViewEngine

is executing. The same controller could function quite well with an

NVelocity view (supported in MvcContrib) since the controller's only coupling to the view is the view name. For

now, we will forward "Hello World3" to the view, and figure 1.10 shows the rendered page. This example has

shown how to get a simple case working, but there are maintenance concerns you should be aware of while

building an application with this framework.

Figure 1.10 Although we are using a complete view, the output is the same as previous examples, except now, we have a full HTML

page and not just an HTML fragment.

1.4 Ensuring the application is maintainable

You might have cringed when you saw that the domain model object was being pushed into an

IDictionary

with

string

key as the way to identify the object in the view. .Net has conditioned us to want everything to be

strongly-typed, so string identifiers are sometimes viewed as a negative. That point is subjective and

controversial, and you have several options depending on your preferences. The use of an

IDictionary<object, object>

for ViewData is the default mechanism in the

Controller

base class. As the

number of objects forwarded to the view increase, it is easy to create some helpers in the view to avoid casting

operations everywhere. Many controllers will only forward one object to the view, and for those cases, we can

make use of the

ViewData.Model

property as well as strongly-typed views. For our next example, we will make

a small change to our controller and view to enable a strongly-typed reference. Listing 1.11 shows our controller

discarding the use of the

IDictionary<object, object>

and passing domain model object directly to the

View()

method. This works well for many scenarios, and it even scales to large application with the use of a

"view model", which is a presentation object specifically crafted for use in a single view. For composed views using

ViewData

as a dictionary may is necessary, but partial views, covered in chapter 4, can also provide for composed

views.

For this view, since our model is a

string

, the only difference is the lack of the need to call

ToString()

the view. Note in listing 1.11 the simplified rendering. If I want to call

ToLower()

to ensure the text was

lowercase, I'd get intellisense and API checking. For this view, we are also using a master page.

Listing 1.11 Passing in the presentation model to the RenderView method

using System.Web.Mvc;

namespace MvcApplication.Controllers

{

public class HelloWorld4Controller : Controller

{

public ActionResult Index()

{

//casting to an object to ensure correct

//overload is called

return View((object)"Hello World4");

}

Listing 1.12 Strongly typed view with master page.

<%@ Page Inherits="System.Web.Mvc.ViewPage<string>"

MasterPageFile="~/Views/Shared/HelloWorld.Master"%>

<%@ Import Namespace="MvcApplication.Controllers"%>

<asp:Content ID="Content2" ContentPlaceHolderID="Main" runat="server">

<h1><%=Model %>! I'm strongly typed in a layout!</h1>

</asp:Content>

Notice that we have a

Model

property available that is the type declared in the Inherits tag. In listing 1.12 we

have chosen

System.Web.Mvc.ViewPage<T>

. The generic base class allows us to strongly-type the

ViewData

property because the

ViewData

property is of type

ViewDataDictionary<T>

, and the

Model

property is of

type

In this example, the view has chosen the master page, but you can also choose the master inside the controller

action. It is up to you, but not all view engines support the view specifying the master. Master pages function

exactly the same as in Web Forms for templating, but the server side postback and

ViewState

mechanism are

irrelevant. Rendering is the only responsibility of the view and the master page. Listing 1.13 shows our master

page, which outlines the structure for the page. The layout declares

System.Web.MVC.ViewMasterPage

as the

base type.

Listing 1.13 The layout for our view. The purpose is to provide the layout structure for the view. Be sure not

to put any behavior here.

<%@ Master Language="C#" AutoEventWireup="true"

Inherits="System.Web.Mvc.ViewMasterPage" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<title>Hello!!</title>

<asp:ContentPlaceHolder ID="head" runat="server">

</asp:ContentPlaceHolder>

</head>

<body>

<asp:ContentPlaceHolder ID="Main" runat="server">

</asp:ContentPlaceHolder>

</div>

</body>

</html>

If we point our browser to

/HelloWorld4

, we see our strongly-typed view and master page in action. To make it

stand out, we have given it a strong, red border as shown in figure 1.11. Most views that we will work with in this

book will use the

ViewPage<T>

base class to enable a strongly-typed

Model

property and the easy usage of view

models, which will be covered in chapter 2.

Figure 1.11. This is our final view, complete with layout, strong typing and a little CSS to spice it up.

Congratulations! You have created your first controller, and it handles its responsibility perfectly. From this

point forward, we will not cover every small step of developing with the MVC Framework. If you are reading this

book, you are already well-versed in ASP.NET, so we will merely be covering the items that are new with the

ASP.NET MVC Framework. We will be using best practices and advanced software development techniques

throughout the examples. The first important practice is unit testing. Because the MVC Framework allows us to

keep our screen controllers separated from the views, we can now test the controlling logic very easily. We

consider testing part of getting started with the MVC Framework, we will cover it now and keep a strong emphasis

on testing throughout this book. Although we will not print every unit test in the book, you can find more unit

tests in the examples available with the book.

1.5 Testing Controller Classes

Turn back to the Visual Studio solution to the unit test project that already exists there. Because Visual Studio

does not come with NUnit, you will need to add your own reference to NUnit or your unit testing framework of

choice. Because MSTest now comes in the Professional sku, the project will come with a reference to MSTest. We

have removed that reference and opted for the more widely used tool, NUnit. We have created a class named

HelloWorld4ControllerTester

to house the unit tests that verify it functions correctly. See in figure 1.12

that we are grouping controller unit test fixtures in a

Controllers

folder. We will continue to group like fixtures.

Browse through the following code listings. You will notice that we have created stubs for several classes that the

controller needs to function. This unit test example is the simplest one we will see in this book. Listing 1.14 depicts

the NUnit test fixture for

HellowWorld4Controller

剩余226页未读，继续阅读

mamama001

粉丝: 5

ASP.NET MVC框架入门与实践

ASP.NET MVC框架深度探索

Manning原版ASP.NET MVC2深度解析

深入浅出ASP.NET MVC框架：从入门到精通

Manning.ASP.NET.MVC.2.in.Action.Jun.2010.pdf

Manning.ASP.NET.MVC2.in.Action 和Apress.Pro.ASP.NET.MVC.2.Framework.2nd.Edition.Jun.2010

asp.net.mvc.4.samples(asp.net.mvc.4实例)

Pro.ASP.NET.MVC.4.pdf

asp.net.mvc

《Apress.Pro.ASP.NET.MVC.3.Framework》PDF版

Web开发新体验_ASP.NET.3.5.MVC架构与实战

最新资源