ASP.NET+C#与MVC实战指南：2010微软官方教程

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

《ASP.NET使用C#和MVC编程指南》是由Microsoft Press出版的一本专业书籍，由Dino Esposito撰写。该书详细介绍了如何在ASP.NET环境中利用C#语言和Model-View-Controller（MVC）架构进行Web开发。作为微软官方技术资料，本书旨在帮助读者掌握.NET框架下的Web应用程序设计和实现。主要内容包括但不限于： 1. **ASP.NET基础知识**：介绍ASP.NET的核心概念，如Web服务器、ASP.NET生命周期、以及它与.NET Framework的关系。读者将了解到ASP.NET如何通过C#提供强大的功能和灵活性。 2. **C#语言基础**：书中会深入浅出地讲解C#语法、面向对象编程、集合类、异步编程等，确保读者对C#有扎实的理解，以便在MVC框架中高效编码。 3. **MVC模式**：这是本书的核心部分，作者会详细解析MVC设计模式，包括模型（Model）、视图（View）和控制器（Controller）的角色划分，以及它们如何协同工作以创建模块化和可维护的Web应用。 4. **Web开发实践**：涵盖HTML、CSS和JavaScript的基础知识，以及如何与ASP.NET结合使用，实现动态网页和交互式用户体验。此外，还会涉及AJAX技术和跨域资源共享（CORS）等现代Web开发技术。 5. **数据库集成**：介绍如何使用ADO.NET连接到SQL Server或其他数据库，进行数据持久化，并演示ORM（对象关系映射）工具，如Entity Framework。 6. **安全性和身份验证**：讨论如何保护Web应用免受攻击，包括认证、授权、HTTPS和Session管理等内容。 7. **调试和性能优化**：书中会分享调试技巧，以及如何通过分析性能瓶颈来提升应用程序的运行效率。 8. **最佳实践和案例研究**：包含实用的开发建议，以及实际项目中的解决方案示例，使读者能够快速理解和应用所学知识。《ASP.NET using c# and MVC.pdf》不仅适合初学者入门，也是中级开发者提升Web开发技能的宝贵参考资料。通过阅读这本书，读者将能够掌握ASP.NET平台上的C#编程和MVC框架，为构建现代Web应用打下坚实基础。

xvi Introduction

Although it’s based on the same runtime environment, ASP.NET MVC is signiﬁcantly different

from ASP.NET Web Forms. It supports a radically different pattern—MVC (actually the special

ﬂavor of MVC known as Model2) rather than a pure Page Controller—and was designed with

a radically different set of goals—testability, extensibility, and closeness-to-the-metal of both

the Web and ASP.NET runtime.

It doesn’t matter what kind of software professional you are, when it comes to choosing the

platform for a new .NET Web application you feel like you are at a crossroads. You know you

have to choose, and you look around for guidance. You see pros and cons on both sides,

and you can hardly see—clearly and tangibly—what’s the right way to go. For this reason,

the core question—should we use ASP.NET Web Forms or ASP.NET MVC—often ends up

being an endless and pointless religious discussion where all parties push their own vision

and scream louder with the gathering force of their conviction.

In the end, the correct answer is that it depends. In the end, the choice is really like Microsoft

describes it: car vs. motorcycle or automatic vs. manual.

This leads to a new and largely unspoken question: Did we really need a second option?

Wouldn’t it have been better for us if Microsoft detected the signs of age of Web Forms

and worked as hard as they worked on ASP.NET MVC to improve that, sticking to just one

framework?

Aren’t two options always better than one? Sure, but two options imply a choice. And

a choice implies information, education, and responsibility. Here’s where this book

hopefully ﬁts in.

ASP.NET MVC and Web Forms

Until late 2008, I was happy enough with Web Forms. I did recognize its weak points and was

able to work around them nicely with discipline and systematic application of design

principles. In the beginning, ASP.NET MVC was enthusiastically received by a relatively small

segment of the community, but one that was screaming loudly and posting a lot. Even

though I’ve never been a member of the ALT.NET community, I’m still constantly keeping

an eye out for any better ways of doing my tasks. So I started to explore the ASP.NET MVC

architecture and tried to understand its potential, while constantly trying to envision concrete

business scenarios in which to employ it. I did this for about a year.

What did I learn?

Technically speaking, ASP.NET MVC is far superior to Web Forms. This is because it’s

newer and was designed around an alternate and more modern set of principles and

patterns. Is this sufﬁcient reason for you to switch to it? In my opinion, it isn’t. ASP.NET

MVC is an excellent choice from the perspective of developers, but that fact alone doesn’t

Introduction xvii

automatically translate into a tangible beneﬁt for the customer and the project. Moreover,

ASP.NET MVC is much less forgiving than Web Forms and requires training, or at least

self-training.

In 10 years of using Web Forms, I’ve seen many professionals with limited programming skills

produce effective Web front ends using data-bound controls and a bit of Microsoft Visual

Basic. This will not happen with ASP.NET MVC. Worse yet, if you start writing ASP.NET MVC

code taking the learn-as-you-go approach that worked for many with Web Forms, you will

surely cook up great examples of much hated spaghetti code.

So learning ASP.NET MVC makes you a better developer, but it has a cost. Who’s supposed

to pay for that? Your customer? Your company? You, yourself? How would you justify to

a project manager the extra training costs for just using ASP.NET MVC? You can try, but the

natural objection is this: “OK, but where’s my return? Can’t we take this project home by

simply using Web Forms, which we already know through and through?”

In the end, picking ASP.NET MVC over Web Forms is a matter of preference and attitude,

or it’s a matter of dealing with some nonfunctional requirements. In the ﬁrst case, you don’t

have extra costs because it can be assumed you know your stuff very well. The second case,

instead, introduces the only scenario I can think of where ASP.NET MVC is a clear winner.

How can you fulﬁll requirements such as strict accessibility, adherence to Web standards,

XHTML, theme-ability, cross-browser experience, and rich AJAX capabilities?

These requirements lead to the necessity of exercising strict control over the markup emitted

for each page. This is an area where ASP.NET MVC is incomparably better than Web Forms,

even when you take into consideration Microsoft’s latest improvements to the ASP.NET 4

framework and your own programming self-discipline.

Every other argument being presented as a plus of ASP.NET MVC—such as testability,

separation of concerns, extensibility, and the like—is just a plus of the framework, not

a breakthrough for the project. By the way, even though in the .NET space we seem to have

discovered testability only a few years ago, it has been listed as a fundamental attribute of

software in the ISO/IEC 9126 paper since 1991. (For more information, have a look at

http://en.wikipedia.org/wiki/ISO_9126.)

Who Is This Book For?

As explained in great detail in Chapter 1, “Goal of ASP.NET MVC and Motivation for Its

Development,” ASP.NET Web Forms is showing the signs of age. And ASP.NET MVC is an

excellent (although still incomplete) replacement. My guess—my humble, two-cent guess—is

that in a couple of years (and in a couple of versions) ASP.NET MVC will offer the same level

of productivity as Web Forms—either because of framework enhancements or because of

xviii Introduction

even more powerful tooling. At that point, you will have two options that are equivalent

functionally and in terms of productivity. But one of them (ASP.NET MVC) can help you write

better code, faster. This may not be the case today with ASP.NET MVC 2, but it likely will be

the case with ASP.NET MVC 3 or 4.

I don’t think that ASP.NET Web Forms will be dismissed very soon. For example, rumors

suggest that ASP.NET Web Forms will move decidedly toward increasing testability in

version 5 through the introduction of some MVP support. We’ll see, but as I see things

ASP.NET MVC is and will remain far superior technically.

Although pushing a team to use ASP.NET MVC today on a project might be an arguable

choice, pushing it within a software company isn’t an arguable choice at all. Having a deep

understanding of ASP.NET MVC makes you a better developer. ASP.NET MVC is easy to pick up

for junior developers who are just out of school, even though it could be harder for experienced

Web Forms developers to learn. This book assumes you have knowledge of Web Forms

programming as it explains how ASP.NET MVC works and how to use it effectively.

My experience shows that too many Web Forms developers built their expertise by trial

and error. ASP.NET MVC requires a sort of reset, and you know that after you reboot your

machine it normally runs faster. But this personal reboot may take a bit of effort. Start

today with ASP.NET MVC, even in parallel with current Web Forms projects. You’ll see the

difference, understand the basic facts of Web development, and soon be ready for writing

better code with both Web Forms and ASP.NET MVC.

Companion Content

This book features a companion Web site that makes available to you all the code used in the

book. This code is organized by chapter, and you can download it from the companion site at

this address: http://go.microsoft.com/fwlink/?LinkId=189142.

Hardware and Software Requirements

You’ll need the following hardware and software to work with the companion content

included with this book:

Microsoft Windows Vista Home Premium Edition, Windows Vista Business Edition,

or Windows Vista Ultimate Edition, Microsoft Windows 7 Home Premium Edition,

Windows 7 Business Edition, or Windows 7 Ultimate Edition, Windows Server 2008, SP1.

Microsoft Visual Studio 2008 Standard Edition, Visual Studio 2008 Enterprise Edition,

or Microsoft Visual C# 2008 Express Edition and Microsoft Visual Web Developer 2008

Express Edition, Visual Studio 2010 Professional Edition, Visual Studio 2010 Premium

Edition, Visual Studio 2010 Ultimate Edition.

剩余589页未读，继续阅读

doig1204

粉丝: 0
资源: 7

ASP.NET+C#与MVC实战指南：2010微软官方教程

ASP.NET MVC5 入门指南.pdf

Pro ASP.NET MVC 5.pdf

ASP .NET using C# VS2008

ASP.NET_Maker_2019.0.1破解版

Csharp.6.0.and.the.NET.4.6.Framework.7th.Edition.1484213335.epub

C#.NET文件下载经典方法.

C# 6.0 and the .NET 4.6 Framework(7th).pdf 2016第7版pdf

Beginning ASP.NET Databases using C#

asp.net mvc chart(MVC 使用chart图表控件的示例）

Pro ASP.NET MVC 5.mobi

最新资源