ASP.NET MVC3详解：构建Web应用

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

"pro.asp.net.mvc3.3rd.edition." 是一本关于ASP.NET MVC3的第三版英文技术书籍，旨在深入介绍该框架的各个方面。本书的内容涵盖了从基础到高级的ASP.NET MVC3技术，帮助读者逐步理解并掌握这一强大的Web应用程序开发框架。以下是书中的主要知识点： 1. **关于作者和技术审阅者** (About the Authors 和 About the Technical Reviewer)：这部分通常会介绍书籍的作者和审阅者，他们的专业背景和在ASP.NET MVC领域的经验，有助于读者了解信息的来源和可靠性。 2. **致谢** (Acknowledgments)：作者可能会感谢对书籍编写过程提供帮助的人或组织，这可能包括贡献代码、反馈意见或提供支持的专业人士。 3. **第一部分：介绍ASP.NET MVC3** (Part1: Introducing ASP.NET MVC3)：这部分从宏观上解释了ASP.NET MVC3的基本概念和核心理念，如模型-视图-控制器（MVC）模式的重要性，以及为什么选择它来构建Web应用。 - **第1章：大想法是什么？** (Chapter1: What’s the Big Idea?)：本章介绍了ASP.NET MVC3框架的基本思想和设计原则。 - **第2章：准备开始** (Chapter2: Getting Ready)：讨论了开始使用ASP.NET MVC3前需要的环境设置和准备工作。 - **第3章：你的第一个MVC应用** (Chapter3: Your First MVC Application)：通过实践指导读者创建首个简单的MVC应用，体验基本工作流程。 - **第4章：MVC模式** (Chapter4: The MVCPattern)：深入探讨MVC模式，包括模型、视图和控制器的角色和交互方式。 - **第5章：核心语言特性** (Chapter5: Essential Language Features)：讲解与ASP.NET MVC3开发相关的编程语言特性，可能是C#或VB.NET。 - **第6章：MVC必备工具** (Chapter6: Essential Tools for MVC)：介绍用于开发ASP.NET MVC应用的工具和环境，如Visual Studio等。 - **第7章至第9章：SportsStore示例应用**：通过一个名为SportsStore的实际项目，进一步讲解应用开发，涵盖导航、购物车和管理功能。 4. **第二部分：ASP.NET MVC3详解** (Part2: ASP.NET MVC3 in Detail)：这部分深入剖析了框架的各种组件和技术。 - **第10章：MVC项目概述** (Chapter10: Overview of MVC Projects)：对MVC项目结构和配置进行详细阐述。 - **第11章：URL、路由和区域** (Chapter11: URLs, Routing, and Areas)：讲解如何定义和管理应用程序的路由规则，以及如何使用区域（Areas）来组织大型项目。 - **第12章：控制器和动作** (Chapter12: Controllers and Actions)：详细介绍了控制器的职责，以及动作方法的定义和执行。 - **第13章：过滤器** (Chapter13: Filters)：讨论了不同类型的过滤器，如授权、异常处理等，以及如何自定义过滤器。 - **第14章：控制器扩展性** (Chapter14: Controller Extensibility)：展示了如何扩展控制器功能以满足特定需求。 - **第15章：视图** (Chapter15: Views)：讲解视图的创建、布局和视图数据的传递。 - **第16章：模型模板** (Chapter16: Model Templates)：介绍了如何使用模板来自定义模型的显示样式。 - **第17章：模型绑定** (Chapter17: Model Binding)：探讨了模型绑定机制，它是如何将HTTP请求数据自动映射到控制器动作参数的。 - **第18章：模型验证** (Chapter18: Model Validation)：讲述了如何实现模型级别的验证规则，确保数据的正确性和一致性。 - **第19章：非侵入式Ajax** (Chapter19: Unobtrusive Ajax)：讲解如何在ASP.NET MVC中使用非侵入式的Ajax技术，以提高用户体验。 - **第20章：jQuery** (Chapter20: jQuery)：讨论了如何结合jQuery库增强ASP.NET MVC应用的交互性和动态性。这些章节提供了全面的ASP.NET MVC3技术指南，无论你是初学者还是有经验的开发者，都能从中获得宝贵的知识和实践经验。下载完整书籍可在www.Pin5i.Com找到。

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

charlesval

粉丝: 0
资源: 2

ASP.NET MVC3详解：构建Web应用

Pro.ASP.NET.MVC.5.5th.Edition

Apress.Pro.ASP.NET.Core.MVC.2.7th.Edition

最终版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.Core.MVC.2.7th.Edition.148423149X

Apress.Pro.ASP.NET.MVC.2.Framework

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

[精通ASP.NET.MVC.5框架(第五版)].Apress.Pro.Asp.Dot.NET.MVC.5.5th.edition.zip

Apress.Pro.ASP.NET.Core.MVC.2.7th.Edition中文(机翻)

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

最新资源