ASP.NET MVC框架入门与深度教程

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

ASP.NET MVC系列教程是一本深入浅出的指南，专为.NET开发者设计，旨在帮助他们掌握ASP.NET MVC框架的各个方面。本书由MEAP（Manning Early Access Program）出版，版权属于2007年的Manning Publications。通过访问曼宁出版社的网站www.manning.com，读者可以获取更多关于此书和其他Manning图书的信息。教程共分为13章，内容涵盖了ASP.NET MVC框架的核心组件和扩展主题，适合初学者和进阶开发者的不同需求。以下是各章节的主要内容概要： 1. **入门**： - 对使用ASP.NET MVC框架的系统要求进行了介绍。 - 包括如何运行预设项目，引导读者逐步体验基础功能。 - 提供一系列"HelloWorld"示例，从简单到复杂，帮助理解框架的工作原理。 - 强调了强类型视图的概念，展示了如何提高代码的清晰度和可维护性。 2. **模型（Model）深入解析**： - 讨论模型在MVC架构中的作用，包括数据访问、业务逻辑和数据验证等方面。 - 详细讲解如何设计和管理应用程序的数据模型。 3. **控制器（Controller）详解**： - 介绍了控制器作为应用程序核心，处理HTTP请求和响应的机制。 - 探讨了如何组织和设计控制器以实现有效的路由和控制流程。 4. **视图（View）深度剖析**： - 展示了视图如何与模型和控制器交互，呈现用户界面。 - 讲解了 Razor 视图引擎，如何编写动态和模板化的HTML。 5. **路由（Routing）**： - 介绍URL映射到控制器和操作的方法，以及如何自定义路由规则。 6. **定制和扩展ASP.NET MVC**： - 涵盖了框架的扩展性，如中间件、特性、插件等，让开发者能够根据项目需求进行定制。 7. **架构扩展至复杂网站**： - 教授如何在大型或复杂的项目中管理和优化MVC架构，以支持高并发和性能优化。 8. **利用现有ASP.NET功能**： - 提醒读者利用.NET框架提供的其他工具和技术，如身份验证、缓存、日志等，增强应用功能。 9. **AJAX在ASP.NET MVC中的应用**： - 详细讲解如何在MVC环境中集成异步JavaScript和XMLHttpRequest技术，提高用户体验。 10. **部署和托管**： - 介绍部署策略，包括IIS设置、Web.config配置，以及云托管选项。 11. **比较 MonoRail 和 Ruby on Rails**： - 对.NET框架之外的其他轻量级Web框架进行对比分析，为开发者提供选择依据。 12. **最佳实践**： - 集中阐述在实际开发中遵循的最佳原则，包括代码组织、测试和性能优化等。 13. **配方（Recipes）**： - 提供一系列实用的解决常见问题和场景的代码片段，便于快速学习和参考。 ASP.NET MVC系列教程是一本全面且深入的教程，无论是初次接触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页未读，继续阅读

MXi4oyu

粉丝: 132
资源: 142

ASP.NET MVC框架入门与深度教程

asp.net.mvc

[ASP.NET.MVC系列].ASPNETMVCQuickly

Wrox.Professional.ASP.NET.MVC.3.Aug.2011.rar

ASP.NET.MVC.4.Web编程].徐雷等.扫描版.pdf

ASP.net.Ajax电子教程

零基础学ASP.NET.2.0动画教程[16-21]

零基础学ASP.NET.2.0动画教程(1-10).rar

ASP.NET MVC3.0系列教程整理

Microsoft.Press.Microsoft.ASP.NET.4.Step.by.Step.Apr.2010

Wrox.Professional.Refactoring.in.CSharp.and.ASP.NET.Apr.2009.pdf

最新资源