深入探索ASP.NET MVC3框架

需积分: 10 57 浏览量更新于2024-07-28 收藏 15.08MB PDF 举报

"Pro ASP.NET MVC3 Framework 是一本深入探讨ASP.NET MVC3框架的专业书籍，旨在帮助开发者理解和掌握这一强大的Web应用程序开发技术。" 在ASP.NET MVC3框架中，核心概念包括模型（Model）、视图（View）和控制器（Controller），它们构成了MVCPattern（模型-视图-控制器模式）。这一模式将应用程序的业务逻辑、数据处理和用户界面分离，提高了代码的可维护性和可测试性。 **第1章：What’s the Big Idea?** 引出了ASP.NET MVC3的重要理念，讨论了它与传统的ASP.NET Web Forms的区别，以及为什么开发者会选择MVC架构。 **第2章：Getting Ready** 提供了开始学习和设置开发环境的基础指导，包括安装所需的软件工具和配置。 **第3章：Your First MVC Application** 指导读者创建第一个MVC应用，涵盖了基本的项目结构和文件布局。 **第4章：The MVCPattern** 进一步深入解析MVC模式，解释模型、视图和控制器各自的角色和职责。 **第5章：Essential Language Features** 介绍了与ASP.NET MVC3相关的C#语言特性，对理解代码编写至关重要。 **第6章：Essential Tools for MVC** 讨论了用于MVC开发的重要工具和最佳实践，包括Visual Studio集成开发环境和调试技巧。 **第7-9章：SportsStore** 通过一个实际的SportsStore应用案例，展示了如何实现购物车、导航和后台管理功能，提供实践经验。 **第10章：Overview of MVC Projects** 对MVC项目的结构和组成进行了全面概述，包括项目模板和配置文件。 **第11章：URLs, Routing, and Areas** 解释了路由系统，如何定义和控制URL模式，以及如何使用Areas来组织大型应用的结构。 **第12-14章：Controllers and Actions, Filters, Controller Extensibility** 探讨了控制器的使用，控制器操作的生命周期，以及如何扩展和过滤控制器行为。 **第15-16章：Views and Model Templates** 讲解了视图的创建和渲染，以及模型模板在视图数据绑定中的应用。 **第17-18章：Model Binding and Model Validation** 描述了模型绑定机制，如何将用户输入自动映射到模型，以及如何实现数据验证。 **第19章：Unobtrusive Ajax** 阐述了如何在MVC中使用无侵入式Ajax技术来创建异步交互，提升用户体验。 **第20章：jQuery** 介绍了jQuery库在ASP.NET MVC中的使用，如何利用它进行DOM操作和事件处理。这本书的内容详尽且深度适中，适合有一定.NET基础的开发者学习和提升ASP.NET MVC3的开发技能。通过阅读和实践书中的示例，读者可以全面了解并掌握该框架的关键技术和最佳实践。

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

edithlva

粉丝: 0
资源: 3

深入探索ASP.NET MVC3框架

Pro ASP.NET MVC 3 Framework

Pro ASP.NET MVC 3 Framework 3rd Edition的源码

Pro ASP.NET MVC3 Framework PDF 扫描高清版

学习asp.net mvc

做为一个初学者，如何学习asp.net mvc

asp.net mvc博客

asp.net mvc bootstrap源码

asp.net mvc vue3

asp.net mvc4 开发指南

asp.net mvc4开发指南 源码

最新资源

asp.net mvc4开发指南源码