精通ASP.NET MVC 3框架：英文版指南

需积分: 10 22 浏览量更新于2024-07-27 收藏 12.48MB PDF 举报

"Pro ASP.NET MVC 3 Framework.pdf 是一本英文版的技术书籍，详细介绍了ASP.NET MVC 3框架。本书旨在引导读者理解并掌握ASP.NET MVC 3的核心概念、工具和最佳实践，通过实例和逐步指导来提升开发技能。内容包括MVC模式的基本原理、编程语言的关键特性、项目构建、URL路由、控制器与动作、过滤器、视图、模型模板、模型绑定、模型验证、无侵入式Ajax以及jQuery的使用等。" 在ASP.NET MVC 3框架中，核心知识点包括： 1. **MVC模式**：MVC（Model-View-Controller）是一种设计模式，用于构建可维护性和可测试性高的Web应用程序。模型负责业务逻辑，视图负责展示数据，而控制器处理用户输入并协调模型和视图。 2. **URLs、Routing和Areas**：URL路由是ASP.NET MVC中的一种关键机制，它允许开发者定义自定义URL模式，使应用程序的URL更具有可读性。Areas则用于将大型应用划分为多个逻辑区域，每个区域可以视为一个独立的小型MVC应用。 3. **Controllers和Actions**：控制器是处理用户请求的对象，包含一系列操作（Actions），这些操作返回视图或执行其他任务。控制器可以使用模型数据填充视图，或者进行业务逻辑处理。 4. **Filters**：过滤器是可重用的代码段，可以应用于控制器或动作，实现如授权、缓存、日志记录等功能。常见的过滤器类型有授权过滤器、异常过滤器、操作结果过滤器和行动过滤器。 5. **Controller Extensibility**：控制器的扩展性允许开发者自定义控制器行为，例如通过继承或实现特定接口来自定义控制器工厂，或者添加额外的行为。 6. **Views**：视图负责呈现数据，通常使用Razor视图引擎来编写。视图可以与强类型化的模型配合，以确保数据安全和类型检查。 7. **Model Templates**：模型模板用于自定义数据类型在视图中的显示方式，提高代码复用和视图的可读性。 8. **ModelBinding**：模型绑定是ASP.NET MVC自动将HTTP请求的数据绑定到控制器操作参数的过程，简化了数据验证和处理。 9. **Model Validation**：模型验证是确保模型数据有效性的过程，ASP.NET MVC支持数据注解验证和服务器端及客户端的联合验证。 10. **Unobtrusive Ajax**：无侵入式Ajax使得JavaScript与服务器端交互更加分离，减少对DOM的直接操作，提高性能和可维护性。 11. **jQuery**：jQuery是广泛使用的JavaScript库，简化了DOM操作、事件处理、动画效果和Ajax交互。在ASP.NET MVC中，jQuery可以与无侵入式Ajax结合，提供流畅的用户体验。本书不仅涵盖了以上基本知识点，还提供了SportsStore这个实际应用案例，帮助读者将理论知识应用于实践，深入理解ASP.NET MVC 3框架的各个方面，从而在实际项目中更有效地利用这一强大的Web开发平台。

CHAPTER 1 ■ WHAT’S THE BIG IDEA?

ASP.NET MVC Is Open Source

Unlike with previous Microsoft web development platforms, you’re free to download the original source

code for ASP.NET MVC, and even modify and compile your own version of it. This is invaluable when

your debugging trail leads into a system component, and you want to step into its code (and even read

the original programmers’ comments). It’s also useful if you’re building an advanced component and

want to see what development possibilities exist, or how the built-in components actually work.

Additionally, this ability is great if you don’t like the way something works, if you find a bug, or if you

just want to access something that’s otherwise inaccessible, because you can simply change it yourself.

However, you’ll need to keep track of your changes and reapply them if you upgrade to a newer version

of the framework. ASP.NET MVC is licensed under the Microsoft Public License (Ms-PL,

http://www.opensource.org/licenses/ms-pl.html), an Open Source Initiative (OSI)–approved open

source license. This means that you can change the source code, deploy it, and even redistribute your

changes publicly as a derivative project. However, Microsoft does not accept patches to the official build.

At present, Microsoft will ship only code that’s the product of its development and quality assurance

(QA) teams. You can download the MVC source code from http://aspnet.codeplex.com/.

Who Should Use ASP.NET MVC?

As with any new technology, the fact of ASP.NET MVC’s existence isn’t a compelling reason to adopt it.

Here, we’ll give you our view of how the MVC Framework compares with the most obvious alternatives.

We’ve tried to be as unbiased as two people writing a book about the MVC Framework can be, but we

know that there is a limit to our objectivity. The following sections are technology-based comparisons.

When selecting a web application framework, you should also consider the skills of your team, the work

involved in porting any existing projects, and your relationship with, and confidence in, the technology

source.

Comparisons with ASP.NET Web Forms

We have already detailed the weaknesses and limitations in traditional ASP.NET Web Forms, and how

ASP.NET MVC overcomes many of those problems. That doesn’t mean that Web Forms is dead, though.

Microsoft has repeatedly stated that both technologies are being actively developed and actively

supported, and that there are no plans to retire Web Forms. In some ways, your choice between the two

is a matter of development philosophy. Consider these points:

• Web Forms takes the view that UIs should be stateful, and to that end, adds a

sophisticated abstraction layer on top of HTTP and HTML, using View State and

postbacks to create the effect of statefulness. This makes it suitable for drag-and-

drop Windows Forms–style development, in which you pull UI widgets onto a

canvas and fill in code for their event handlers.

• MVC embraces HTTP’s true stateless nature, working with it rather than fighting

against it. The MVC Framework requires you to understand how web applications

actually work. Given that understanding, it provides a simple, powerful, modern

approach to writing web applications, with tidy code that’s easier to extend and

maintain over time, and that’s free of bizarre complications and painful

limitations.

CHAPTER 1 ■ WHAT’S THE BIG IDEA?

There are certainly cases where Web Forms is at least as good as, and probably better than, MVC.

The obvious example is small, intranet-type applications that are largely about binding grids directly to

database tables or stepping users through a wizard. Web Forms drag-and-drop development strengths

can outweigh its weaknesses when you don’t need to worry about bandwidth consumption or search

engine optimization.

If, on the other hand, you are writing applications for the Internet or larger intranet applications,

you will be attracted by the bandwidth efficiencies, better browser compatibility, and better support for

automated testing that MVC offers.

Migrating from Web Forms to MVC

If you have an existing ASP.NET Web Forms project that you are considering migrating to MVC, you will

be pleased to know that the two technologies can coexist in the same application. This provides an

opportunity to migrate existing applications gradually, especially if the application is partitioned into

layers with domain model or business logic constrained separately to the Web Forms pages.

In some cases, you might even deliberately design an application to be a hybrid of the two

technologies.

Comparisons with Ruby on Rails

Rails has become a benchmark against which other web platforms are compared. Developers and

companies who are in the Microsoft .NET world will find ASP.NET MVC far easier to adopt and learn,

whereas developers and companies that work in Python or Ruby on Linux or Mac OS X will find an easier

path to Rails. It’s unlikely that you would migrate from Rails to ASP.NET MVC or vice versa. There are some

real differences in scope between the two technologies.

Rails is a holistic development platform, meaning that it handles the complete stack, right from

database source control, through ORM, to handling requests with controllers and actions—all topped off

with built-in automated testing tools.

The ASP.NET MVC Framework focuses on handling web requests in an MVC-pattern with

controllers and actions. It does not have a built-in ORM tool, a built-in automated testing tool, or a

system for managing database migrations. This is because the .NET platform already has an enormous

range of choices for these functions, and you can use any of them. For example, if you’re looking for an

ORM tool, you might use NHibernate, Subsonic, Microsoft’s Entity Framework, or one of the many other

mature solutions available. Such is the luxury of the .NET platform, although this does mean that these

components are not as tightly integrated into ASP.NET MVC as the equivalents are into Rails.

Comparisons with MonoRail

MonoRail is an earlier .NET-based MVC web application platform, created as part of the open source

Castle project and in development since 2003. In many ways, MonoRail acted as the prototype for

ASP.NET MVC. MonoRail demonstrated how a Rails-like MVC architecture could be built on top of

ASP.NET and established patterns, practices, and terminology that are used throughout Microsoft’s

implementation.

We don’t see MonoRail as a serious competitor. It is probably the most popular .NET web

application platform created outside Redmond, and it did achieve reasonably widespread adoption in its

day. However, since the launch of ASP.NET MVC, the MonoRail project is rarely heard of. The

momentum of enthusiasm and innovation in the .NET web development world is now focused on

ASP.NET MVC.

CHAPTER 1 ■ WHAT’S THE BIG IDEA?

What’s New in ASP.NET MVC 3

The headline feature in MVC version 3 is the introduction of the Razor View Engine. Previous versions of

MVC have relied on the standard ASP.NET view engine, which depends on the ASP.NET <% and %> blocks

(if you have done any kind of ASP.NET development, you are certain to have seen these in use).

The Razor View Engine replaces the traditional blocks with the @ character. The new notation is

quicker to write and faster to compile than the old view engine. It also has more flexible features and

allows for better unit testing.

You can still use the previous approach, but the Microsoft team has made it clear that Razor is the

future for MVC. And, in fact, we have used Razor for all of the examples in this book.

Razor isn’t the only enhancement in MVC 3. The Visual Studio project tooling has been streamlined

and there is better support for dependency injection. It also provides improved support for the JSON

data format and JavaScript, including tighter integration with jQuery.

Summary

In this chapter, we have described how web development has evolved at tremendous speed from the

primordial swamp of the CGI executable to the latest high-performance, standards-compliant, agile

platforms. We reviewed the strengths, weaknesses, and limitations of ASP.NET Web Forms, Microsoft’s

main web platform since 2002, and the changes in the wider web development industry that forced

Microsoft to respond with something new.

You saw how the ASP.NET MVC platform addresses the weaknesses of ASP.NET Web Forms, and

how its modern design delivers advantages to developers who want to write high-quality, maintainable

code.

In the next chapter, you’ll see the MVC Framework in action, learning the simple mechanisms that

yield all these benefits. By Chapter 7, you’ll be ready for a realistic e-commerce application built with a

clean architecture, proper separation of concerns, automated tests, and beautifully minimal markup.

剩余836页未读，继续阅读

shangxunjishu

粉丝: 0
资源: 5

精通ASP.NET MVC 3框架：英文版指南

深入理解ASP.NET MVC 3框架

使用Pro ASP.NET MVC 2 Framework构建高性能Web应用

2009年Apress ASP.NET MVC Framework权威指南

Pro ASP.NET MVC Framework.pdf

Pro ASP.NET MVC 2 Framework.pdf

Pro.ASP.NET.MVC.3.Framework.pdf

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

Pro ASP.NET MVC 3 Framework_PDF_With_Code

Pro.ASP.NET.MVC.4.pdf

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

最新资源