深入探索ASP.NET MVC框架

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

"ASP.NET MVC in Action" 本书"ASP.NET MVC in Action"是关于微软的ASP.NET MVC框架的一部深入实践的指南。ASP.NET MVC（Model-View-Controller）是一种用于构建可测试、灵活且高性能的Web应用程序的开源框架。该书涵盖了从基础到高级的主题，旨在帮助开发者充分利用这个强大的框架。在第一章"Getting started with the ASP.NET MVC Framework"中，作者介绍了使用ASP.NET MVC框架所需的系统需求，以及如何运行初始项目。这一章以一个逐步进阶的"Hello, World"示例开始，帮助读者快速入门。此外，书中还讲解了强类型视图（Strongly-typed views），这种特性允许开发人员在视图中直接使用模型对象，从而提高代码的类型安全性和可维护性。在路由基础知识部分，作者详细阐述了ASP.NET MVC中的URL路由机制，这是一种允许开发者自定义URL模式以提高用户体验和SEO优化的方法。通过配置路由规则，开发者可以控制请求如何映射到控制器的行动方法。接下来的章节进一步深入探讨了各个核心组件： - 第二章"The Model in depth"涵盖了数据模型的设计，包括数据验证和业务逻辑的实现。 - 第三章"The Controller in depth"讨论了控制器的作用，它是模型和视图之间的桥梁，处理用户输入并决定应用程序的响应。 - 第四章"Views in depth"则专注于视图的创建和渲染，以及如何使用各种视图辅助方法（View Helpers）来生成HTML。 - 第五章"Routing"更深入地讨论了路由配置和高级用法。 - 第六章"Customizing and extending the ASP.NET MVC Framework"介绍了如何自定义和扩展框架以满足特定项目需求。 - 第七章"Scaling the architecture to more complex sites"讨论了如何将ASP.NET MVC应用于大型、复杂网站的架构设计。 - 第八章"Leveraging existing ASP.NET features"介绍了如何利用现有的ASP.NET功能，如身份验证、授权和状态管理。 - 第九章"AJAX in ASP.NET MVC"涵盖了在MVC应用程序中集成异步JavaScript和XML技术。 - 第十章"Hosting and deployment"讲解了部署ASP.NET MVC应用到生产环境的最佳实践。 - 第十一章"Exploring Mono Rail and Ruby on Rails"提到了与其他Web框架，如Mono Rail和Ruby on Rails的比较。 - 第十二章"Best practices"提供了关于开发ASP.NET MVC应用时应遵循的最佳实践和指导原则。 - 最后的第十三章"Recipes"提供了一些解决常见问题和挑战的实用代码片段。这本书是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页未读，继续阅读

李必胜

粉丝: 2
资源: 1

深入探索ASP.NET MVC框架

ASP.NET MVC in Action.pdf

asp.net mvc in action

Manning ASP.NET MVC In Action Source Code

Manning ASP.NET MVC In Action Source Code 5

Manning ASP.NET MVC In Action Source Code 6

Manning ASP.NET MVC In Action Source Code 4

Manning ASP.NET MVC In Action Source Code 2

Manning ASP.NET MVC In Action Source Code 3

ASP.NET MVC in Action: 探索技术细节与实战

Asp.net MVC In Action 第2版：面向初学者的Web开发指南

最新资源