深入探索ASP.NET MVC 3：构建动态Web应用

.ASP.NET

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

"ASP.NET MVC 3 是微软推出的一款用于构建数据驱动、性能高效动态Web应用程序的最新框架。这本书深入解析了ASP.NET MVC 3的新特性，由微软内部团队撰写，旨在帮助开发者掌握如何安装和创建ASP.NET MVC项目，并通过MVC Music Store教程强化实践应用。" 《ASP.NET MVC 3 高级编程》是一本详细指导开发者的著作，涵盖了从入门到进阶的全过程。ASP.NET MVC是一个基于模型-视图-控制器（MVC）设计模式的框架，它提供了一种分离关注点的方式，使得开发者能够更清晰地组织代码，提高代码的可测试性和可维护性。书中的Part 1 "Introducing ASP.NET MVC 3"介绍了MVC的基本理念和准备事项。第一章"什么是大想法？"解释了ASP.NET MVC 3的核心概念，第二章"Getting Ready"讨论了开始前的准备工作，第三章"Your First MVC Application"引导读者创建第一个MVC应用，第四章"The MVCPattern"深入探讨了MVC模式的设计原理。第五章至第七章主要讲解了语言特性和实际应用工具。第五章"Essential Language Features"涵盖了ASP.NET MVC所使用的语言关键特性，第六章"Essential Tools for MVC"介绍了一些对MVC开发至关重要的工具，而第七章"SportsStore: A Real Application"则通过一个体育用品商店的实例展示了如何在实际项目中运用这些知识。第八章至第十九章深入剖析了ASP.NET MVC 3的细节。包括URL路由、控制器与动作、过滤器、控制器扩展性、视图、模型模板、模型绑定、模型验证以及不显眼的Ajax。这些章节不仅详细讲解了每个组件的工作方式，还提供了实际应用场景的指导。第二十章"jQuery"则讨论了与ASP.NET MVC 3集成的JavaScript库jQuery，它是实现客户端交互和动态更新的关键技术。这本书适合想要深入了解ASP.NET MVC 3的开发者，无论是初学者还是有经验的程序员，都可以从中获取到丰富的知识和实践经验。通过阅读和实践，读者将能够利用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.

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页未读，继续阅读

xie196807

粉丝: 0
资源: 2

深入探索ASP.NET MVC 3：构建动态Web应用

Ext.NET.MVC.Pro.2.2.0.MVC.Examples.Explorer.zip

精通Asp.net MVC3(英文名字：Wrox.Professional.ASP.NET.MVC.3.Aug.2011)

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

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

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

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

Wrox.Professional.ASP.NET.MVC.3.Aug.2011 [epub格式]

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

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

ASP.NET.MVC.

最新资源