深入探索ASP.NET MVC框架

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

"asp.net mvc in action英文原版 - 一本深入探讨ASP.NET MVC框架的书籍" 本书是关于ASP.NET MVC框架的专业指南，由Manning Publications出版，通过其早期访问计划（MEAP Edition）提供。书中涵盖了从基础到高级的各种主题，旨在帮助读者全面理解和掌握ASP.NET MVC的各个关键组成部分。在《ASP.NET MVC in Action》中，作者详细介绍了以下几个核心知识点： 1. **系统要求与框架入门**：首先，书中会阐述开发ASP.NET MVC应用所需的系统环境，以及如何运行书中的示例项目，让读者快速上手。 2. **渐进式“Hello, World”示例**：通过一系列逐步深入的实例，读者可以学习如何创建基本的ASP.NET MVC应用程序，理解控制器、模型和视图之间的交互。 3. **强类型视图**：强类型视图是ASP.NET MVC中的一个重要概念，它允许开发者在视图层直接利用模型数据，提高了代码的类型安全性和可维护性。 4. **路由基础**：路由是ASP.NET MVC中控制URL结构的关键机制，书中详细讲解了如何配置和自定义路由规则，以便更好地控制应用程序的导航和URL模式。 5. **模型深入研究**：深入探讨模型层的设计和实现，包括数据访问、业务逻辑和验证规则，帮助开发者构建健壮的后端逻辑。 6. **控制器深入研究**：详细讲解控制器的职责、动作方法和结果，以及如何利用控制器处理用户请求和生成响应。 7. **视图深入研究**：讨论视图模板、辅助方法和布局页面，以创建动态、响应式的用户界面。 8. **扩展和定制ASP.NET MVC**：介绍如何根据项目需求对框架进行扩展和定制，包括自定义过滤器、模型绑定器等。 9. **架构扩展到更复杂的网站**：讨论如何将ASP.NET MVC应用于大型项目，管理复杂性并确保可伸缩性。 10. **利用现有ASP.NET特性**：展示如何集成和利用ASP.NET平台的其他功能，如身份验证、授权、缓存等。 11. **ASP.NET MVC中的AJAX**：讲解如何在ASP.NET MVC中集成AJAX技术，以实现无刷新的用户体验。 12. **托管与部署**：涵盖应用程序的发布、配置和在不同环境下的部署策略。 13. **探索Mono Rail和Ruby on Rails**：对比ASP.NET MVC与其他类似框架，如Mono Rail和Ruby on Rails，帮助读者拓宽视野。 14. **最佳实践与食谱**：提供一系列经过实战检验的技巧和策略，帮助开发者遵循最佳实践，解决常见问题。通过这些章节，本书旨在为读者提供一个全面的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页未读，继续阅读

Java学习训练营

粉丝: 99
资源: 19

深入探索ASP.NET MVC框架

ASP.NET MVC in Action.pdf

[ASP.NET MVC] ASP.NET MVC 4 实战 (英文版)

精通ASP.NET MVC 4：英文原版指南

Asp.NET MVC 5 高级编程第5版 完整版 文字版 英文版.pdf

asp.net.mvc

Manning原版ASP.NET MVC2深度解析

ASP.NET MVC 1.0 入门教程

ASP国际化多语言详细方案

【java毕业设计】校内跑腿业务系统源码（springboot+vue+mysql+说明文档）.zip

【java毕业设计】大学志愿填报系统源码（springboot+vue+mysql+说明文档）.zip

最新资源

Asp.NET MVC 5 高级编程第5版完整版文字版英文版.pdf