ASP.NET MVC 3 框架入门与详解

5星 · 超过95%的资源需积分: 10 110 浏览量更新于2024-07-27 收藏 9.26MB PDF 举报

"Pro.ASP.NET.MVC.3.Framework 是一本深入探讨ASP.NET MVC 3框架的专业书籍，旨在帮助读者理解和应用这一强大的Web开发技术。本书涵盖了从基础到高级的各种主题，通过实例教学来引导读者逐步掌握MVC设计模式和ASP.NET MVC 3的核心特性。" 在ASP.NET MVC 3框架中，MVC代表模型-视图-控制器（Model-View-Controller），这是一种用于构建可维护、可扩展和高度分化的Web应用程序的设计模式。以下是书中涉及的一些关键知识点： 1. **模型（Model）**: 模型是应用程序的数据层，负责业务逻辑和数据管理。在ASP.NET MVC 3中，你可以使用Entity Framework或其他ORM（对象关系映射）工具来处理数据库操作。 2. **视图（View）**: 视图是用户看到并与之交互的页面。它通常由Razor或ASPX视图引擎创建，负责展示模型中的数据。视图应保持无逻辑状态，只负责渲染模型数据。 3. **控制器（Controller）**: 控制器是应用程序的中枢，接收来自用户的请求，处理这些请求，与模型交互，并决定返回哪个视图给用户。控制器可以使用Action方法来响应不同的HTTP请求。 4. **URL路由（URL Routing）**: ASP.NET MVC 3使用路由系统来定义URL模式，使URL更符合语义化，提高SEO友好性。开发者可以自定义路由规则，将特定的URL映射到控制器的特定Action上。 5. **过滤器（Filters）**: 过滤器是一种可以添加到控制器或Action上的行为，如授权、异常处理、缓存等。它们提供了一种方便的方式来处理跨切面关注点。 6. **区域（Areas）**: 当项目变得复杂时，可以使用区域来组织相关的控制器和视图，形成一个子应用程序，有助于代码的结构化和模块化。 7. **控制器扩展性（Controller Extensibility）**: ASP.NET MVC 3允许开发者扩展控制器的行为，例如通过实现自定义的控制器基类或控制器工厂。 8. **视图引擎（View Engine）**: 书中有提到Razor视图引擎，这是ASP.NET MVC 3引入的新引擎，以其简洁的语法和高效的性能受到开发者欢迎。 9. **模型绑定（Model Binding）**: 自动将HTTP请求数据绑定到控制器Action的参数，简化了数据验证和处理。 10. **模型验证（Model Validation）**: ASP.NET MVC 3提供了内置的验证机制，可以通过数据注解进行客户端和服务器端验证。 11. **无侵入式AJAX（Unobtrusive AJAX）**: 书中还讨论了如何使用无侵入式JavaScript技术来实现AJAX功能，使得更新页面部分更加整洁且易于维护。 12. **jQuery**: jQuery库在ASP.NET MVC 3中广泛使用，用于简化DOM操作、事件处理和AJAX交互。这本《Pro.ASP.NET.MVC.3.Framework》详细介绍了ASP.NET MVC 3框架的各个方面，包括基础概念、实际应用以及高级技术，对于希望深入了解和使用该框架的开发者来说是一份宝贵的资源。

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.

Download at www.Pin5i.Com

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.

Download at www.Pin5i.Com

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.

Download at www.Pin5i.Com

剩余836页未读，继续阅读

刘彦玮

粉丝: 1
资源: 14

ASP.NET MVC 3 框架入门与详解

Pro.ASP.NET.MVC.3深度解析：从入门到实战(第3版)

Pro.ASP.NET.MVC3 Framework详解与实战

Apress Pro ASP.NET MVC 3框架深度解析与实战指南

Apress.Pro.ASP.NET.MVC.3.Framework

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

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

Pro.ASP.NET.MVC.3.Framework电子书及源码

最终版Pro.ASP.NET.MVC.3.Framework(3rd Edition)

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

Apress.Pro.ASP.NET.MVC.4.Framework

最新资源