Apress ASP.NET MVC 3框架详解：从入门到实战

ASP.NET.MVC

需积分: 9 166 浏览量更新于2024-07-26 收藏 12.43MB PDF 举报

"Apress.Pro.ASP.NET.MVC.3.Framework"是一本深度介绍ASP.NET MVC 3框架的入门指南，适合对Web开发感兴趣的读者学习和提升技能。本书由经验丰富的作者编写，旨在为初学者提供全面且实用的知识，从基础概念到实际项目的开发流程都有详尽的讲解。在第一部分，"Introducing ASP.NET MVC 3"，作者通过生动的案例，如Chapter 1 "What's the Big Idea?"，引导读者理解MVC（Model-View-Controller）模式的核心理念，以及它如何在Web开发中提高代码组织和用户体验。Chapter 2 "Getting Ready" 探讨了开发环境的设置和准备工作，确保读者具备开发MVC应用的基础条件。随着学习的深入，Chapter 3 至Chapter 7 针对核心组件进行了深入剖析。"Your First MVC Application" 演示了构建第一个完整项目的步骤，而Chapter 4 "The MVCPattern" 则详细解释了MVC模式的各个角色和交互方式。接下来的章节涉及语言特性（Chapter 5）、必备工具（Chapter 6）、以及一个实际的SportsStore应用实例，包括导航、购物车和后台管理功能的实现（Chapter 7 至Chapter 9）。第二部分"ASP.NET MVC 3 in Detail"深化了对框架的理解，涵盖了项目概述（Chapter 10）、URL管理、路由和区域划分（Chapter 11），控制器与动作的设计（Chapter 12），以及过滤器的使用（Chapter 13）。这部分还探讨了控制器扩展性（Chapter 14）、视图（Chapter 15）和模型模板（Chapter 16）的重要性。模型绑定（Chapter 17）和验证（Chapter 18）是确保数据准确无误的关键环节，而Chapter 19 的Unobtrusive Ajax技术则展示了现代Web开发中的异步交互。最后，Part 3 "Delivering Successful ASP.NET MVC 3 Projects" 结束于实战技巧，如jQuery的集成（Chapter 20），帮助读者掌握如何将所学知识应用于实际项目，以交付高质量的Web应用。这本书不仅提供了ASP.NET MVC 3框架的扎实理论基础，还通过实例演示和实用技巧，帮助读者逐步成长为一名熟练的ASP.NET MVC开发者。无论是初次接触该框架还是希望进一步提升技能的开发人员，都应珍藏这本书作为宝贵的学习资源。

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

jubao_liang

粉丝: 40
资源: 7

Apress ASP.NET MVC 3框架详解：从入门到实战

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

Apress.Pro.Entity.Framework.Core.2.for.ASP.NET.Core.MVC.2018

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

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

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

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

Apress.Pro.Csharp.5.0.and.the.NET.4.5.Framework.Aug.6th.Edition.2012

Apress.Mobile.ASP.NET.MVC.5.Nov.2013

Apress.ASP.NET.MVC.4.Recipes

最新资源