A Practical Guide to ASP.NET MVC 3 Framework for Beginners

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

"Pro.ASP.NET.MVC.3.Framework" 是一本专门针对 ASP.NET MVC 3 框架的深入指南，它在市面上相对稀缺，旨在帮助开发人员理解和掌握 ASP.NET MVC 3 的核心概念和技术。这本书适合有一定基础的开发者，无论是初学者还是希望提升技能的专业人士，都能从中受益匪浅。在本书中，作者以清晰易懂的方式介绍了 ASP.NET MVC 3 的设计理念和实践。首先，第1章"What’s the Big Idea?" 开篇就阐述了 MVC（模型-视图-控制器）架构模式的优势和在 Web 开发中的重要性，让读者对 MVC 3 的整体框架有所了解。第2章"Getting Ready" 为读者提供了必要的准备工作，包括环境设置和基本配置。接下来的章节逐步深入，第3章"Your First MVC Application" 实战演示如何创建和运行第一个 MVC 项目，使理论与实践相结合。第4章"MVCPattern" 全面解析 MVC 设计模式，强调其分层结构以及如何提高代码组织的清晰度。随后的章节分别讲解了关键的语言特性（Chapter 5）、必备工具（Chapter 6），以及如何构建一个完整的体育用品商店应用（SportsStore，包括导航、购物车和后台管理功能，分别在Chapters 7-9）。 Part 2 的内容更加细致入微，从第10章开始，读者可以了解到 MVC 项目的概述，接着是 URL 路由、区域划分（Chapter 11）、控制器和动作的设计（Chapter 12），以及如何使用过滤器来增强应用程序的功能（Chapter 13）。控制器的可扩展性（Chapter 14）和视图（Chapter 15）的深入探讨，帮助开发者掌握 MVC 的核心组件。第16章"Model Templates" 和第17章"Model Binding" 讲解模型模板的使用和数据绑定技术，确保数据的正确处理。模型验证在第18章中占据重要位置，而无侵入式Ajax（Chapter 19）则展示了如何优化用户体验。最后，第20章"jQuery" 教授如何结合 MVC 3 与流行的前端库 jQuery 进行开发。总体而言，"Pro.ASP.NET.MVC.3.Framework" 是一本全面而实用的教程，不仅提供理论指导，还有丰富的示例和案例，对于提升 ASP.NET MVC 3 技能，解决实际开发问题具有很高的价值。无论是想要学习 MVC 或者提升 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.

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

zaishuiyiren

粉丝: 0

A Practical Guide to ASP.NET MVC 3 Framework for Beginners

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

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

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

asp.net和java web的异同

asp.net.mvc图书管理系统参考文献资料

出十道ASP.NET Core MVC 判断题

asp.net core mvc

学习asp.net mvc

ASP.NET从入门到精通 书本重点内容

asp.net core web应用与asp.net web应用一样吗？

最新资源

ASP.NET从入门到精通书本重点内容