深入探索ASP.NET MVC 3框架

PDF文件

下载需积分: 10 | 12.48MB | 更新于2024-07-28 | 163 浏览量 | 举报收藏

立即下载

"Apress Pro ASP.NET MVC 3 Framework 是一本深入介绍微软平台上的ASP.NET MVC框架的专业书籍，尤其关注其在设计模式、干净架构和可测试性方面的应用。本书第一部分旨在帮助读者理解ASP.NET MVC 3的基础理念，包括新特性，并通过实践体验框架的使用。" ASP.NET MVC 是一个针对Web开发者的重大转变，它强调了清晰的架构、设计模式和可测试性，并不试图掩盖Web的工作原理。书中通过不同的章节逐步引导读者进入ASP.NET MVC的世界。在书的前言部分，读者可以找到作者和审阅者的信息，以及对他们的感谢。这部分内容对于了解书籍的背景和权威性是很有帮助的。第一部分“介绍ASP.NET MVC 3”包含了以下章节： 1. 第1章“大想法是什么？”：这部分可能讲解了ASP.NET MVC框架的核心概念和它与传统Web开发的区别，以及ASP.NET MVC 3的新特性。 2. 第2章“准备就绪”：可能涵盖了开始使用ASP.NET MVC 3之前需要的环境设置和工具安装。 3. 第3章“你的第一个MVC应用程序”：引导读者创建并运行第一个基本的ASP.NET MVC应用，以实践学习。 4. 第4章“MVC模式”：深入讨论模型-视图-控制器模式的工作原理及其在ASP.NET MVC中的应用。 5. 第5章“基本语言特性”：介绍了C#或VB.NET等编程语言在ASP.NET MVC中的关键特性和用法。 6. 第6章“MVC必备工具”：探讨用于开发ASP.NET MVC应用的各种工具和最佳实践。 7. 第7章“SportsStore：一个真实的应用程序”：通过构建一个体育用品商店应用来实践ASP.NET MVC的使用。 8. 第8章“SportsStore：导航和购物车”：涵盖如何实现应用的导航功能和购物车逻辑。 9. 第9章“SportsStore：管理界面”：讲解后台管理系统的实现，如用户管理、商品管理等。第二部分“ASP.NET MVC 3详解”更深入地探讨了框架的技术细节： 10. 第10章“MVC项目的概述”：提供项目结构、配置文件等方面的概述。 11. 第11章“URLs、路由和区域”：详细阐述了URL路由规则的设定和区域（Areas）的概念，用于管理大型应用的结构。 12. 第12章“控制器和动作”：讲解控制器类的编写和动作方法的定义，以及它们如何响应HTTP请求。 13. 第14章“过滤器”：讨论了如授权、异常处理等过滤器的使用。 15. 第15章“视图”：介绍了视图的创建和渲染，包括Razor视图引擎的使用。 16. 第16章“模型模板”：讨论了如何自定义数据绑定的显示模板。 17. 第17章“模型绑定”：解释了如何自动将表单数据绑定到模型对象。 18. 第18章“模型验证”：涵盖了客户端和服务器端的数据验证机制。 19. 第19章“非侵入式Ajax”：介绍了如何在ASP.NET MVC中优雅地实现Ajax功能。 20. 第20章“jQuery”：讨论了与ASP.NET MVC配合使用的JavaScript库jQuery，以及如何在MVC应用中利用它增强用户体验。第三部分“交付成功的ASP.NET MVC 3项目”则可能涵盖项目管理、测试、部署以及最佳实践等内容，确保读者能够将所学知识应用于实际开发环境中，成功完成ASP.NET MVC项目。通过这本书，读者将全面掌握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.

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

pazzachl

粉丝: 0

深入探索ASP.NET MVC 3框架

Apress Pro ASP.NET MVC 3 Framework(2011-07-09)

Apress Pro ASP.NET MVC 3 Framework 教程：从入门到实战

Apress Pro ASP.NET MVC 3 Framework 第三版：alpha预览更新概览

Apress - Pro ASP.NET MVC Framework

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

Pro ASP.NET MVC 2 Framework(最新Apress关于mvc 2.0权威著作)

pro-asp.net-mvc-2-framework:史蒂文·桑德森（Steven Sanderson）的“ Pro ASP.NET MVC 2 Framework”源代码-mvc source code

Pro ASP.NET MVC 2 Framework, Second Edition (Expert's Voice in .NET)

Asp.net MVC 3 Framework

探索Pro ASP.NET MVC 3 Framework源代码

Pro ASP.NET MVC 3 Framework 第三版预览：架构与新特性深度解析

《Pro ASP.NET MVC 2 Framework 2nd Edition》：高性能微软平台Web应用开发指南

2013年Apress专业ASP.NET MVC 4框架详解

Pro ASP.NET MVC 2 .Framework

2009年Apress ASP.NET MVC Framework权威指南

2013年Apress《Pro ASP.NET MVC 4框架》权威指南

【微信小程序】From表单（88/100）

slf4j-log4j12-2.0.0-alpha4.jar中文文档.zip

最新资源