精通ASP.NET网站后台开发：C#语言实践指南

需积分: 10 167 浏览量更新于2024-07-18 收藏 15.67MB PDF 举报

"这是一本关于学习ASP.NET网站后台开发的书籍，主要使用微软的C#语言进行讲解，涵盖了从基础的.NET框架介绍到高级的Web应用开发技术。" 本书详细介绍了ASP.NET开发的各项核心概念和技术，旨在帮助读者掌握如何构建高效、功能丰富的网站后台程序。书中分为四个部分： 1. **第一部分：介绍.NET** - 第1章《大图景》：概述.NET框架的基本结构和用途，以及它在现代Web开发中的地位。 - 第2章《C#语言》：深入解析C#编程语言的基础语法和特性，包括变量、控制流、类和对象等。 - 第3章《类型、对象和命名空间》：探讨.NET中的数据类型、面向对象编程以及代码组织方式。 2. **第二部分：开发ASP.NET应用程序** - 第4章《Visual Studio》：讲解使用Visual Studio作为开发环境的技巧，包括项目设置、调试和部署。 - 第5章《Web表单基础》：介绍Web表单的概念和工作原理，是构建动态网页的关键。 - 第6章《Web控件》：讲解各种内置Web控件的使用，如文本框、按钮、下拉列表等，以及自定义控件的创建。 - 第7章《错误处理、日志记录和跟踪》：教授如何处理程序运行时的错误，以及实现有效的日志记录和性能跟踪。 - 第8章《状态管理》：讨论在Web环境中保持用户状态的不同方法，如视图状态、隐藏字段和Cookie等。 3. **第三部分：构建更好的Web表单** - 第9章《验证》：介绍验证用户输入的方法，确保数据质量和安全性。 - 第10章《富控件》：涵盖更复杂的UI组件，如图表、网格和树形视图等，提升用户体验。 - 第11章《用户控件和图形》：讲解如何创建和使用自定义用户控件，以及在Web应用中处理图像和图形。 - 第12章《样式、主题和主页面》：介绍如何通过样式表、主题和主页面来统一网站外观和布局。 - 第13章《网站导航》：教授如何设计和实现网站的导航结构，提供良好的用户体验。 4. **第四部分：处理数据** - 第14章《ADO.NET基础》：详解ADO.NET库，它是.NET框架中用于数据库交互的核心组件。 - 第15章《数据绑定》：介绍如何将数据源与UI控件绑定，实现数据驱动的Web应用。通过阅读本书，读者将能够从零开始学习ASP.NET，逐步掌握C#编程，建立功能完善的Web应用程序，并与数据库进行有效交互。无论你是初学者还是有经验的开发者，这本书都提供了丰富的实例和实践指导，有助于提升你在ASP.NET开发领域的技能。

CHAPTER 1 ■ THE BIG PICTURE

Sometimes the division between these components isn’t clear. For example, the term ASP.NET is sometimes

used in a narrow sense to refer to the portion of the .NET class library used to design web pages. On the other

hand, ASP.NET also refers to the whole topic of .NET web applications, which includes .NET languages and many

fundamental pieces of the class library that aren’t web-speciﬁc. (at’s generally the way we use the term in this

book. Our exhaustive examination of ASP.NET includes .NET basics, the C# language, and topics that any .NET

developer could use, such as component-based programming and database access.)

Figure 1-4 shows the .NET class library and CLR—the two fundamental parts of .NET.

ADO.NET

Data Access

XML

Web Forms

File I/O

Core System Classes (Threading, Serialization, Reflection,

Collections, and So On)

The .NET Class Library

Compiler and Loader

Code Verification and Optimization

Memory Management and Garbage Collection

Code Access Security

(Other Managed Code Services)

The Common Language Runtime

Windows Forms

(And So On)

Figure 1-4. e .NET Framework

CHAPTER 1 ■ THE BIG PICTURE

In the remainder of this chapter, you’ll take a quick look at the ingredients that make up the .NET

Framework.

C#, VB, and the .NET Languages

is book uses the Visual Basic language, which enables you to create readable, modern code. e .NET version

of VB is similar in syntax to older ﬂavors of VB that you may have encountered, including “classic” VB 6 and the

Visual Basic for Applications (VBA) language often used to write macros in Microsoft Ofﬁce programs such as

Word and Excel. However, you cannot convert classic VB into the .NET ﬂavor of Visual Basic, just as you cannot

convert C++ into C#.

is book uses C#, Microsoft’s .NET language of preference. C# resembles Java, JavaScript, and C++ in

syntax, so programmers who have coded in one of these languages will quickly feel at home.

Interestingly, VB and C# are quite similar. ough the syntax is dierent, both VB and C# use the .NET class

library and are supported by the CLR. In fact, almost any block of C# code can be translated, line by line, into an

equivalent block of VB code (and vice versa). An occasional language dierence pops up, but for the most part,

a developer who has learned one .NET language can move quickly and efﬁciently to another. ere are even

software tools that translate C# and VB code automatically (see http://converter.telerik.com or

http://tangiblesoftwaresolutions.com for examples).

In short, both VB and C# are elegant, modern languages that are ideal for creating the next generation of web

applications.

Note ■ .NET 1.0 introduced completely new languages. However, the changes in subsequent versions of .NET

have been more subtle. Although the version of C# in .NET 4.5 adds a few new features, most parts of the

language remain unchanged. In Chapter 2 and Chapter 3, you’ll sort through the syntax of C# and learn the

basics of object-oriented programming.

Intermediate Language

All the .NET languages are compiled into another lower-level language before the code is executed. is lower-

level language is the Common Intermediate Language (CIL, or just IL). e CLR, the engine of .NET, uses only

IL code. Because all .NET languages are based on IL, they all have profound similarities. is is the reason that

the VB and C# languages provide essentially the same features and performance. In fact, the languages are so

compatible that a web page written with C# can use a VB component in the same way it uses a C# component,

and vice versa.

e .NET Framework formalizes this compatibility with something called the Common Language

Speciﬁcation (CLS). Essentially, the CLS is a contract that, if respected, guarantees that a component written in

one .NET language can be used in all the others. One part of the CLS is the common type system (CTS), which

deﬁnes the rules for data types such as strings, numbers, and arrays that are shared in all .NET languages. e

CLS also deﬁnes object-oriented ingredients such as classes, methods, events, and quite a bit more. For the most

part, .NET developers don’t need to think about how the CLS works, even though they rely on it every day.

Figure 1-5 shows how the .NET languages are compiled to IL. Every EXE or DLL ﬁle that you build with a

.NET language contains IL code. is is the ﬁle you deploy to other computers. In the case of a web application,

you deploy your compiled code to a live web server.

CHAPTER 1 ■ THE BIG PICTURE

Note ■ You might wonder why .NET compilers don’t compile straight to machine code. The reason is that the

machine code depends on several factors, including the CPU. If you compile an application to machine code on one

computer, there’s no guarantee that it will work on another computer with a different processor.

e Common Language Runtime

e CLR is the engine that supports all the .NET languages. All .NET code runs inside the CLR. is is true

whether you’re running a Windows application or a web service. For example, when a client requests an ASP.NET

web page, the ASP.NET service runs inside the CLR environment, executes your code, and creates a ﬁnal HTML

page to send to the client.

Not only does the CLR execute code, but it also provides a whole set of related services such as code

veriﬁcation, optimization, and object management. e implications of the CLR are wide-ranging:

Deep language integration: VB and C#, like all .NET languages, compile to IL. In other

words, the CLR makes no distinction between dierent languages—in fact, it has no

way of knowing what language was used to create an executable. is is far more than

mere language compatibility; it’s language integration.

Side-by-side execution: e CLR also has the ability to load more than one version of

a component at a time. In other words, you can update a component many times,

and the correct version will be loaded and used for each application. As a side eect,

multiple versions of the .NET Framework can be installed, meaning that you’re able to

upgrade to new versions of ASP.NET without replacing the current version or needing

to rewrite your applications.

Fewer errors: Whole categories of errors are impossible with the CLR. For example,

the CLR prevents many memory mistakes that are possible with lower-level languages

such as C++.

Along with these truly revolutionary beneﬁts, the CLR has some potential drawbacks. Here are two issues

that are sometimes raised by new developers but aren’t always answered:

Performance: A typical ASP.NET application is extremely fast, because ASP.NET code

is compiled to machine code before it’s executed. However, processor-crunching

algorithms still can’t match the blinding speed of well-written C++ code, because

the CLR imposes some additional overhead. Generally, this is a factor only in a few

performance-critical high-workload applications (such as real-time games). With

high-volume web applications, the potential bottlenecks are rarely processor-related

but are usually tied to the speed of an external resource such as a database or the web

server’s ﬁle system. With ASP.NET caching and some well-written database code, you

can ensure excellent performance for any web application.

Code transparency: IL is much easier to disassemble, meaning that if you distribute

a compiled application or component, other programmers may have an easier

time determining how your code works. is isn’t much of an issue for ASP.NET

applications, which aren’t distributed but are hosted on a secure web server.

CHAPTER 1 ■ THE BIG PICTURE

e .NET Class Library

e .NET class library is a giant repository of classes that provide prefabricated functionality for everything

from reading an XML ﬁle to sending an e-mail message. If you’ve had any exposure to Java, you may already be

familiar with the idea of a class library. However, the .NET class library is more ambitious and comprehensive

than just about any other programming framework. Any .NET language can use the .NET class library’s features

by interacting with the right objects. is helps encourage consistency among dierent .NET languages and

removes the need to install numerous components on your computer or web server.

Some parts of the class library include features you’ll never need to use in web applications (such as the

classes used to create desktop applications with Windows interfaces). Other parts of the class library are targeted

directly at web development. Still more classes can be used in various programming scenarios and aren’t speciﬁc

to web or Windows development. ese include the base set of classes that deﬁne common variable types and

the classes for data access, to name just a few. You’ll explore the .NET Framework throughout this book.

You can think of the class library as a well-stocked programmer’s toolkit. Microsoft’s philosophy is that it will

provide the tedious infrastructure so that application developers need only to write business-speciﬁc code. For

example, the .NET Framework deals with thorny issues such as database transactions and concurrency, making

sure that hundreds or thousands of simultaneous users can request the same web page at once. You just add the

logic needed for your speciﬁc application.

Visual Studio

e last part of .NET is the Visual Studio development tool, which provides a rich environment where you can

rapidly create advanced applications. Although in theory you could create an ASP.NET application without Visual

Studio (for example, by writing all the source code in a text editor and compiling it with .NET’s command-line

compilers), this task would be tedious, painful, and prone to error. For that reason, all professional ASP.NET

developers use a design tool such as Visual Studio.

Some of the features of Visual Studio include the following:

Page design: You can create an attractive page with drag-and-drop ease by using Visual

Studio’s integrated web form designer. You don’t need to understand HTML.

Automatic error detection: You could save hours of work when Visual Studio detects

and reports an error before you run your application. Potential problems are

underlined, just like the “spell-as-you-go” feature found in many word processors.

Debugging tools: Visual Studio retains its legendary debugging tools, which allow you

to watch your code in action and track the contents of variables. And you can test web

applications just as easily as any other application type, because Visual Studio has a

built-in web server that works just for debugging.

IntelliSense: Visual Studio provides statement completion for recognized objects and

automatically lists information such as function parameters in helpful tooltips.

You’ll learn about all these features in Chapter 4, when you consider the latest version of Visual Studio.

It’s also important to note that Visual Studio is available in several editions:

Visual Studio Express for Web:

is is a completely free version of Visual Studio that’s

surprising capable. Its main limitation is that it allows you to build web applications

and components only, not other types of .NET programs (for example, Windows

applications).

剩余899页未读，继续阅读

songxiangsheng

粉丝: 2
资源: 2

精通ASP.NET网站后台开发：C#语言实践指南

asp.net网站后台模板

asp.net网站后台管理模板

ASP.NET网站后台

ASP.NET网站后台框架

5个asp.net网站后台模板

asp.net网站后台（附源码）

零码漂亮的ASP.NET网站后台框架

JQuery实现的经典ASP.NET网站后台框架

基于jQuery实现的asp.net网站后台框架

ASP.NET网吧后台管理网站系统

最新资源