ASP.NET MVC 3框架入门与实战详解

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

"Pro.ASP.NET.MVC.3.Framework" 是一本针对初学者和专业开发者的经典教程，专注于ASP.NET MVC 3框架的全面介绍与深入探讨。该教材以一种循序渐进的方式引领读者理解并掌握ASP.NET MVC 3的核心概念和技术，适合希望通过MVC架构构建高效、可维护的Web应用程序的开发者。在本书的第一部分，作者从介绍MVC（Model-View-Controller）模式的理念开始，逐步引导读者如何准备环境和创建第一个MVC应用程序。章节3详细讲述了如何通过实际操作来体验和构建一个基础的体育商店应用，这有助于读者将理论知识转化为实践。随着对MVC模式的理解加深，第4章进一步剖析了MVC的核心组成部分，包括模型（Model）、视图（View）和控制器（Controller）的角色及其交互。接着，作者介绍了ASP.NET MVC 3中的关键语言特性和工具，例如第5章的必备语言功能和第6章的MVC开发工具。进入第二部分，内容更加深入。第10章概述了MVC项目的整体结构和管理，而第11章重点讲解URL路由、区域划分等概念，这对于构建灵活的网站架构至关重要。第12至19章分别围绕控制器、动作、过滤器、控制器扩展性、视图、模型模板、模型绑定、模型验证以及无侵入式Ajax技术展开，这些是MVC开发中的核心技能。最后，第20章介绍了jQuery的集成，这在现代Web开发中是不可或缺的一部分，它能提升用户体验并简化前端交互。通过这本书，读者不仅能掌握ASP.NET MVC 3的基础，还能学习到实际项目开发中的实践经验，从而提升Web开发水平。整个教程旨在帮助读者建立扎实的MVC开发基础，并能在实际工作中灵活运用所学知识，无论是初学者还是有经验的开发者都能从中受益匪浅。想要深入理解并实践ASP.NET MVC 3的朋友们，这本电子书将是你不可或缺的学习资源。

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

懵懂

粉丝: 1181
资源: 32

ASP.NET MVC 3框架入门与实战详解

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

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

Pro.ASP.NET.MVC.3.Framework.pdf

Pro.ASP.NET.MVC.3.Framework电子书及源码

最终版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.MVC.2.Framework

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

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

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

最新资源