精通ASP.NET MVC 1.0：英文完整版

4星 · 超过85%的资源需积分: 10 105 浏览量更新于2024-08-02 收藏 17.92MB PDF 举报

"Professional ASP.NET MVC 1.0(完整版) 是一本深入学习ASP.NET MVC框架的专业书籍，英文版提供了全面的技术指导。" 在ASP.NET MVC框架中，开发人员可以构建灵活、可测试和可维护的Web应用程序。这本书详细介绍了这一强大的技术，帮助读者从基础到高级全面掌握其核心概念。 1. **模型-视图-控制器(MVC)**：MVC是一种设计模式，它将应用程序分为三个主要组件：模型（Model）负责数据管理，视图（View）负责用户界面呈现，控制器（Controller）处理用户交互并协调模型与视图。书中第一章“NerdDinner”通过一个实际的例子介绍了如何使用ASP.NET MVC搭建一个完整的应用。 2. **ASP.NET与ASP.NET MVC的对比**：在第二章中，作者探讨了传统的ASP.NET Web Forms与ASP.NET MVC的区别，解释了为什么MVC更适合某些类型的应用程序，并强调了MVC在分离关注点和测试驱动开发方面的优势。 3. **路由和URL**：第三章“Routes and URLs”深入讲解了ASP.NET MVC中的路由机制，它是决定请求如何映射到控制器行动的关键。读者会学习如何自定义URL结构，以提高可读性和SEO友好性。 4. **控制器**：第五章介绍了控制器的职责，包括接收HTTP请求、操作模型数据、选择合适的视图以及返回响应。控制器是连接模型和视图的桥梁，允许开发人员实现业务逻辑。 5. **视图**：第六章“Views”关注视图的创建和渲染，讲解了Razor语法和弱类型视图，以及如何使用视图数据和辅助方法来动态生成HTML。 6. **AJAX支持**：第七章“AJAX”展示了如何在ASP.NET MVC中集成异步JavaScript和XML技术，提升用户体验，实现页面的部分刷新。 7. **过滤器**：第八章“Filters”讨论了动作过滤器，如授权、日志记录和异常处理，它们可以在控制器行动前后自动执行，简化代码复用。 8. **安全与身份验证**：第九章“Securing Your Application”涵盖了Web应用程序的安全性，包括用户认证、授权和防止跨站脚本攻击(XSS)等。 9. **测试驱动开发(TDD)**：第十章“Test Driven Development with ASP.NET MVC”介绍了如何利用TDD方法编写可测试的代码，以及如何使用工具如NUnit进行单元测试和集成测试。本书通过丰富的示例代码和实践指导，帮助读者深入了解ASP.NET MVC，提升Web开发技能。同时，书中还提供了在线资源，如Wrox社区、论坛和章节下载，以便读者进一步学习和交流。无论你是初学者还是有经验的开发者，这本书都能为你提供宝贵的洞见和实用技巧。

xiv

Contents

The Modal Popup with jQuery 296

The Modal Popup Code 297

The Rating Control 299

Summary 303

Filters 30Chapter 8: 5

Filters Included with ASP.NET MVC 305

Authorize 306

OutputCache 308

Exception Filter 310

Custom Filters 311

Writing a Custom Action Filter 316

Writing a Custom Authorization Filter 317

Writing a Custom Exception Filter 319

Filter Ordering 320

Filter Naming 321

Summary 323

Securing Your Application 32Chapter 9: 5

This Is a War 327

Knowing Your Enemy’s Mind 327

Weapons 331

Spam 331

Case Study: Proﬁ ting from Evil with the Srizbi and Storm Botnets 332

Digital Stealth Ninja Network 333

Threat: Cross-Site Scripting (XSS) 334

Passive Injection 334

Active Injection 336

Preventing XSS 338

Html.AttributeEncode and Url.Encode 338

Threat: Cross-Site Request Forgery 339

Preventing CSRF Attacks 342

Threat: Cookie Stealing 343

Preventing Cookie Theft with HttpOnly 344

Keeping Your Pants Up: Proper Error Reporting and the Stack Trace 345

Securing Your Controllers, Not Your Routes 345

Using [Authorize] to Lock Down Your Action or Controller 346

Using [NonAction] to Protect Public Methods 346

Whitelist Form Binding 347

Summary: It’s Up to You 348

84619book.indb Listxiv84619book.indb Listxiv 3/30/09 2:09:09 PM3/30/09 2:09:09 PM

Introduction

Why does the world need Yet Another Web Framework?

This is the question that is most likely on your mind — or perhaps it’s what you were thinking when

you saw this book sitting on the shelf. We each asked ourselves this many times over the last few years.

Indeed there are many frameworks out there today ﬂ avored with every buzzword the industry can think

of. In short, it’s easy to be skeptical. Yet as we, the authors, delve deeper into the latest and greatest web

framework, we’re each starting to realize just how far the industry has come in the last 10 years.

Rob began programming for the Web with Classic ASP in 1997 and was giddy with excitement. When .NET

came out, he remembers running around his ofﬁ ce, stopping everyone from working and explaining that

the world just tilted on its axis.

We all feel the same way about ASP.NET MVC. Not because it’s “something different” but because it

offers developers the ultimate chance to “do it their way.” You don’t like the way the platform renders

the View? Change it! Just about every part of the ASP.NET MVC Framework is “swappable” — if the

shoes pinch, get different shoes. Don’t like ties? Why not a bow tie? You’re totally in control.

ASP.NET MVC is a web framework that comes with a bunch of conventions to make your life easier

when you follow them, but if you don’t want them, the framework is quick to step out of your way so

that you can get your work done in the way you like.

This book is going to go into the “out-of-the-box” experience you’ll have with ASP.NET MVC, but more

importantly you’ll learn practical ways that you can extend ASP.NET MVC with your own magic —

then hopefully share that magic with others.

Because of this extensibility and attention to “doing it your way,” we’re happy to embrace Yet Another

Web Framework and hope you are willing to come along with us for the ride.

Who This Book Is For

This book is for web developers who are looking to add more complete testing to their web sites, and

who are perhaps ready for “something different.”

In some places, we assume that you’re somewhat familiar with ASP.NET Web Forms, at least peripher-

ally. There are a lot of ASP.NET Web Forms developers out there who are interested in ASP.NET MVC,

so there are a number of places in this book where we contrast the two technologies. Even if you’re not

already an ASP.NET developer, you might still ﬁ nd these sections interesting for context, as well as for

your own ediﬁ cation, as ASP.NET MVC may not be the web technology that you’re looking for.

It’s worth noting, yet again, that ASP.NET MVC is not a replacement for ASP.NET Web Forms. Many

web developers have been giving a lot of attention to other web frameworks out there (Ruby on Rails,

84619flast.indd Listxvii84619flast.indd Listxvii 3/31/09 5:34:34 AM3/31/09 5:34:34 AM

Introduction

xviii

Django), which have embraced the MVC (Model-View-Controller) application pattern, and if you’re one

of those developers, or even if you’re just curious, this book is for you.

MVC allows for (buzzword alert!) a “greater separation of concerns” between components in your

application. We’ll go into the ramiﬁ cations of this later on, but if it had to be said it in a quick sentence:

ASP.NET MVC is ASP.NET Unplugged. ASP.NET MVC is a tinkerer’s framework that gives you very ﬁ ne-

grained control over your HTML and JavaScript, as well as complete control over the programmatic

ﬂ ow of your application.

There are no declarative server controls in MVC, which some people may like, others may dislike. In the

future, the MVC team may add declarative view controls to the mix, but these will be far different from

the components that ASP.NET Web Forms developers are used to, in which a control encapsulates both the

logic to render the view and the logic for responding to user input etc. Having all that encapsulated in a

single control in the view would violate the “separation of concerns” so central to this framework. The lev-

els of abstraction have been collapsed, with all the doors and windows opened to let the air ﬂ ow freely.

The ﬁ nal analogy we can throw at you is that ASP.NET MVC is more of a motorcycle, whereas ASP.NET

Web Forms might be more like a minivan, complete with airbags and a DVD player in case you have kids

and you don’t want them to ﬁ ght while you’re driving to the in-laws for Friday dinner. Some people like

motorcycles, some people like minivans. They’ll both get you where you need to go, but one isn’t techni-

cally better than the other.

How This Book Is Structured

This book is divided into three very broad sections, each comprising several chapters.

The ﬁ rst third of the book is concerned with introducing the MVC pattern and how ASP.NET MVC

implements that pattern.

Chapter 1 starts off with a description of the Model-View-Controller pattern, explaining the basic con-

cepts of the pattern and providing a bit of its history. The chapter goes on to describe the state of the

MVC pattern on the Web today as it is implemented by various frameworks, such as ASP.NET MVC.

Chapter 2 covers the ways that ASP.NET MVC is different from ASP.NET Web Forms and how to get

ASP.NET MVC up and running.

Chapter 3 explores the structure of a standard MVC application and covers what you get out of the box.

It covers some of the conventions and the digs a little under the hood to take a look at the entire request

lifecycle for an ASP.NET MVC request.

Chapter 4 digs deep into routing to describe the role that URLs play in your application and how routing

ﬁ gures into that. It also differentiates routing from URL rewriting and covers a bit on extending routing

and writing unit tests for routes.

Chapter 5 takes a look at controllers and controller actions — what they are and how to write them.

It also covers action results, which are returned by controller actions and what they are used for.

Chapters 6–7 cover views and view engines, and then add a little ﬂ avor on top by examining the role

that AJAX plays in your views.

84619flast.indd Listxviii84619flast.indd Listxviii 3/31/09 5:34:34 AM3/31/09 5:34:34 AM

剩余459页未读，继续阅读

xshf12345

粉丝: 59
资源: 23

精通ASP.NET MVC 1.0：英文完整版

Professional ASP.NET MVC 1.0.pdf

Professional ASP.NET MVC 1.0.pdf Book

ASP.NET MVC 1.0详解：专业指南

ASP.NET MVC 1.0 教程：从零开始学习

ASP.NET MVC 1.0 学习指南：从零开始

ASP.NET MVC 1.0 中文教程：创建与CRUD操作

ASP.NET MVC学习指南：从入门到实践

(完整版)Professional Asp.net MVC 1.0

asp.net 中使用oracle数据库事务

Ext.Net2.0

最新资源