ASP.NET MVC深度探索：从入门到实践与最佳实践

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

《ASP.NET.MVC.in.Action》是一本专门探讨ASP.NET MVC框架的指南，由MEAPEdition的ManningEarlyAccessProgram出版于2007年。该书旨在为读者提供全面的ASP.NET MVC技术理解，包括但不限于框架的基本概念、应用开发流程和最佳实践。在第一章"Getting Started with the ASP.NET MVC Framework"中，作者介绍了使用ASP.NET MVC框架所需的系统要求，引导新手逐步入门。读者可以学习如何运行起始项目，并通过一系列渐进式“HelloWorld”示例来熟悉环境。书中强调了强类型视图的概念，这是ASP.NET MVC架构的一个关键特性，它能提高代码的可维护性和清晰度。第二到四章深入剖析了MVC模型（Model）、控制器（Controller）和视图（View）的工作原理。模型负责数据处理和业务逻辑，控制器处理用户请求并调用模型，而视图则负责渲染HTML并呈现给用户。这些章节详细解释了如何构建和组织这三个组件之间的交互。第五章探讨路由（Routing），这是URL与控制器动作之间映射的核心机制，对于构建灵活的URL结构至关重要。通过学习，开发者能够创建自定义路由规则，以更好地控制网站的导航。第六章涉及定制和扩展ASP.NET MVC框架，让读者了解如何根据需求扩展框架的功能或进行二次开发。这包括对框架核心组件的深入理解以及如何编写插件或自定义组件。第七章讨论如何将架构扩展到更复杂的网站，涉及性能优化、模块化设计以及大型项目的架构设计策略。第八章聚焦于利用现有的ASP.NET功能，如身份验证、缓存和异步处理等，使读者能够充分利用现有的技术栈。第九章专门讲述AJAX在ASP.NET MVC中的应用，讲解如何实现非阻塞用户体验和数据的局部刷新，增强Web应用程序的交互性。第十章涵盖了ASP.NET MVC的部署和主机选项，包括本地开发环境设置、云部署和容器化部署等实用知识。第十一章对比分析了ASP.NET MVC与MonoRail和Ruby on Rails等其他Web框架，帮助读者理解选择ASP.NET MVC的理由及可能的替代方案。最后两章，第十二章“Best Practices”提供了开发过程中的最佳实践建议，以及第十三章“Recipes”则包含了解决常见问题的实战指南，为实际开发工作提供了实用的解决方案。《ASP.NET.MVC.in.Action》是一本全面且深入的指南，适合初学者和有经验的开发者提升他们的ASP.NET MVC技能，是构建现代Web应用不可或缺的参考资料。

}

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页未读，继续阅读

wwwer42223

粉丝: 1
资源: 2

ASP.NET MVC深度探索：从入门到实践与最佳实践

asp.net.mvc

[ASP.NET.MVC系列].ProASPnetMVCFramework

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

ASP.NET.MVC.in.Action

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

Manning.ASP.NET.MVC.in.Action

ASP.NET.MVC.4.in.Action

Manning.ASP.NET.MVC.4.in.Action

ASP.NET.MVC系列，详细介绍MVC用法

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

最新资源