Visual C# .NET 开发完全指南

需积分: 1 180 浏览量更新于2024-07-26 收藏 9.17MB PDF 举报

"Visual C# .NET Developer's Handbook" 《Visual C# .NET Developer's Handbook》是一本专为学习和精通Visual C# .NET编程的开发者准备的教材。这本书由John Paul Mueller编写，由SYBEX Inc.出版，旨在提供一个全面的指南，帮助读者深入理解并实践使用Visual C#进行.NET应用程序开发。该书涵盖了Visual C# .NET的关键知识点，包括但不限于： 1. **C#语言基础**：讲解了C#的基本语法、数据类型、控制结构、函数、类和对象等核心概念，使初学者能够快速上手编程。 2. **.NET Framework**：介绍了.NET Framework的架构，包括Common Language Runtime (CLR)、类库以及如何利用它来创建跨平台的应用程序。 3. **Windows Forms**：详细阐述了如何使用Visual C#构建用户界面，包括控件使用、事件处理和对话框的集成，帮助开发者创建交互式桌面应用。 4. **ASP.NET**：探讨了使用C#开发Web应用程序的方法，包括页面生命周期、控件和服务器端脚本，以及如何与数据库交互。 5. **ADO.NET**：深入讲解了访问和操作数据库的机制，如DataSet、DataTable、DataAdapter等，以及如何实现数据绑定和数据源控制。 6. **异常处理和调试**：讨论了错误处理的最佳实践，包括try-catch语句和调试技巧，以帮助开发者在遇到问题时能快速定位和修复错误。 7. **多线程编程**：解释了如何在.NET环境中使用多线程，包括同步、线程安全和并发控制，这对于构建高效和响应迅速的应用至关重要。 8. **XML和Web服务**：介绍XML作为数据交换格式的使用，以及如何创建和消费Web服务，为实现分布式系统提供支持。 9. **代码调试和测试**：提供了有关调试工具和单元测试的指导，帮助确保软件质量。 10. **程序设计模式**：讲解了常见的设计模式，如工厂模式、单例模式和观察者模式，以提高代码的可读性和可维护性。书中还可能包含实际示例代码和练习，以便读者可以亲手实践，加深理解。此外，技术编辑Ross Russell Mullen的审校确保了书中技术内容的准确性和实用性。该书的附带CD-ROM可能包含源代码、示例项目和相关开发工具，方便读者直接运行和学习。通过阅读和实践《Visual C# .NET Developer's Handbook》，开发者不仅可以掌握Visual C# .NET的编程技巧，还能了解.NET开发的最佳实践，从而提升其在IT行业的专业技能。

assemblies are an ordered method of packaging an application or an application unit such as a

component.

Attributes

Attributes are special features that enable you to describe an application that would normally

require code. For example, you can use an attribute to define an event receiver or an event

source. A single word or short set of words serves to augment some code within an

application or a component.

So, why is this feature so important? Imagine writing the components you always have in the

past, but with as little as 25% of the code you use today. Less code means fewer potential

errors and a shorter development time. Programmers from all walks are finding they have a

hard time meeting delivery dates, and are given shorter deadlines and increasing application

complexity. Any technology that promises to reduce development time using a tool that you're

already familiar with is a welcome relief.

We'll use attributes a lot throughout the book. Attributes are such a useful feature that using

them is an essential part of learning C#. Once you learn how to use the built-in attributes,

we'll also discuss creating custom attributes. Using custom attributes can significantly

improve an already great feature. (See the section titled "An Attribute Example" in Chapter 3

for details.)

Other Language Interoperatiblity

All of the .NET languages are designed to work together with relative ease. In fact, you can

use a mixed language environment when scripting. A component you create in C# will work

with Visual Basic because both use the same IL. Mixing and matching languages that rely on

the .NET Framework doesn't require much work. If you want to use a Visual Basic

component in your C# application, simply place the component in the project folder or

Working with non-.NET languages is a little harder, but not impossible. You can use your

managed component in an unmanaged application, or your unmanaged component in a

managed application. Microsoft provides a special namespace:

System.Runtime.InteropServices and some special attributes to make interoperability easier.

We'll discuss this topic further as the book progresses.

Understanding the Benefits of Using C#

In the previous sections of the chapter, you learned what C# is and what it has that you didn't

have before. This is important, but some developers will still say, "So what?" Yes, C# does

solve many problems that developers have with older languages, but experienced developers

already know how to get around those issues and may see C# as yet another language to learn.

The fact is that C# has a lot to offer developers from a personal perspective. I wouldn't say

any of these features are earth shattering, and you've probably heard these promises for other

languages in the past. C# actually delivers on these promises and makes life easier for the

developer. Will C# make you a better programmer? Yes, in some ways. For example, it helps

更多电子书教程下载请登陆http://down.zzbaike.com/ebook

本站提供的电子书教程均为网上搜集，如果该教程涉及或侵害到您的版权请联系我们。

you catch more errors before they become problems. However, only experience creates great

programmers.

Most developers will find that C# makes them faster and more efficient programmers. You'll

spend less time figuring out how to code something due to an ambiguity in the development

environment. In many cases, you'll also find that you spend less time searching for just the

right API call or switch that isn't documented.

Now that you have some idea of what you have to gain from C#, let's discuss the topic in

detail. The following sections answer the question, "What will C# do for me?" You'll learn

why C# is such an important improvement in the development community.

Developer Productivity Enhancements

There's one overriding reason to use C#-it's the language of choice for many developers who

work extensively with COM or other object-based development technologies. Spending even

a small amount of time on the microsoft.public.dotnet.csharp.general,

microsoft.public.dotnet.vb.general, and microsoft.public.dotnet.vc.general newsgroups shows

widespread developer interest in C# as a language. (You can find all of these newsgroups on

the news://news.microsoft.com server, if you can't find them on your local ISP.) Many

developers on these newsgroups already plan to move to C# because it alleviates so many

application development problems. In addition, Microsoft has submitted C# to the European

standards group, ECMA (http://www.ecma.ch/), which means that the language will benefit

from the efforts of a standards committee. (The http://www2.hursley.ibm.com/tc39/ website

contains a better description of the standards effort.) Finally, more than one company is

interested in C#, which could mean some level of platform independence for the language.

The high interest in this language, coupled with a standards-oriented approach, means that

developers will want to adopt C# relatively quickly.

Now that we've covered the main reason to move to C#, let's talk about all of the reasons to

use it. The following sections will tell you about the benefits of C#, the prototyping and

development speed, and how you can use C# to create better COM+ applications.

Simplicity

C# adds simplicity to the development environment in several ways. We've already talked

about how Microsoft has simplified the data types by consolidating some and adding others.

For example, you no longer need to worry about which char data type to use-there's only one.

Likewise, the new decimal data type will greatly reduce programming complexity.

The use of the .NET Framework will simplify matters as well. The hierarchical structure of

namespaces will make it easier to find methods that you need. In addition, more system

resources are available as methods, rather than API calls. For example, with C# you can now

write event log entries using a simple method call, rather than using the convoluted method

for Visual C++.

One item I haven't mentioned yet is the IDE provided with Visual Studio .NET. Microsoft has

added a variety of automation features to the product. For example, when you type a

statement name, the IDE will automatically add the required braces for you. This feature

更多电子书教程下载请登陆http://down.zzbaike.com/ebook

本站提供的电子书教程均为网上搜集，如果该教程涉及或侵害到您的版权请联系我们。

won't necessarily save a lot of time, but it should reduce the number of simple coding errors

that programmer will have to find before an application compiles.

Managed environments simplify programming tasks. For example, C# will greatly reduce

memory leaks using garbage collection. Of course, the use of garbage collection will also

reduce debugging time because the programmer will have fewer errors to find. Since memory

leaks are notoriously difficult to find and fix, most developers will find that garbage collection

greatly reduces the amount of debugging time for a given project.

Consistency

There are many new types of consistency within C#. However, three forms deserve special

mention because they have such a great impact on the development environment.

Everything is an object. C# even treats variables as objects. The runtime environment

"boxes" variables into an object when you need to perform a task like data conversion. Once

the data conversion is finished, the variable is unboxed. The point is that you can access

everything in the same way-there aren't any special rules to remember.

The .NET Framework ensures function call consistency. Instead of having to remember a

lot of very odd API calls, you just follow a hierarchy of namespace entries to the method you

need to perform a specific task. Since every call is handled in the same way, the developer

only needs to worry about the task at hand, rather than try to remember the odd exception to

the rule that an API call might require.

Error trapping is easier than ever before. Unlike Visual C++ and Visual Basic where there

are a number of ways to detect errors, C# uses a single standard method. This means that

developers can standardize error-trapping routines and reduce the complexity of finding and

eradicating problems like data entry errors.

Modern Development Options

Visual C++ and other languages were developed at a time when the Desktop was king.

Vendors updated these languages with moderate success for the world of client/server

programming. In the past few years, Internet development has become the area where most

developers spend their time. Updates to these older languages now feel like kludges added to

compensate for a development environment that vendors never designed these languages to

address.

Given the need for distributed applications today, it's time for a new language that's designed

to better meet the needs of modern developers. C# is that language. The use of a modern IDE

and programming techniques will allow developers to gain the level of operating system

access they require. We've talked about all of these features throughout this briefing, so I

won't cover them again here.

Object Orientation

Unlike Visual C++ and Visual Basic, C# provides true object orientation. Everything is an

object. This language does make some concessions for the sake of performance, but even in

these areas, C# provides the means to use objects. For example, C# stores and uses variables

更多电子书教程下载请登陆http://down.zzbaike.com/ebook

本站提供的电子书教程均为网上搜集，如果该教程涉及或侵害到您的版权请联系我们。

in the same way that Visual C++ and Visual Basic have in the past. The difference is that C#

can box a variable within an object, making it easy to access the variable as an object when

needed. This means that C# provides the same level of object orientation that languages like

Eiffel and Smalltalk do, but without the performance penalties.

C# also embraces the COM+ virtual object system. This means that all objects execute within

a context. You can assign role-based security to objects, which means that you can allow user

interaction based on the role the user has within an organization. In short, you have much

finer control over the component execution environment.

Finally, C# gets rid of the global variables, methods, and constants. Everything appears within

a class. This means there are fewer chances for naming conflicts and the data contained within

variables remains safer. While it will take some developers time to get used to the new

method of handling data, the result is more reliable components and applications.

Compatibility

C# provides an environment that's compatible with everything that has gone before. If you

really want to use the old APIs that you used in C programs long ago, C# provides a means to

access them. Likewise, you have access to standard COM and OLE Automation through the

APIs you've used in the past. C# provides access to all of the required data types through the

COM+ runtime.

Flexibility

You'll find that C# is extremely flexible. It can't quite do everything that Visual C++ can. For

example, if you need a native code output such as a DLL or EXE, then Visual C++ is the only

choice when using Visual Studio .NET. However, in all other ways, C# is more flexible than

anything that has gone before. You obtain all of the best features of Visual Basic and Visual

C++ in one package.

Faster Prototyping and Development

To provide an honest evaluation in this section, you have to separate the benefits of using the

new Visual Studio .NET IDE from the benefits of using C#. For example, everyone has

access to the autocomplete and help features that the Visual Studio .NET IDE provides. While

the new IDE does help you work faster, you'd also receive this benefit when using other

languages.

C# provides its own set of productivity features. The way Microsoft put the language together

means you'll spend less time guessing and more time writing code. You don't have to worry

about pointers any longer. That alone should save both development and debugging time.

You'll also find that the organizational benefits of C# help you prototype and develop

applications faster. The consistent look of every class you create means you spend less time

worrying about structure and more time coding your project. However, as with any other new

product, you'll spend some time overcoming the C# learning curve before you actually see the

benefits of the new way of creating classes.

更多电子书教程下载请登陆http://down.zzbaike.com/ebook

本站提供的电子书教程均为网上搜集，如果该教程涉及或侵害到您的版权请联系我们。

When C# Isn't the Right Choice

Developers are always looking for the silver bullet-the solution that works every time.

Unfortunately, there aren't any silver bullets in the computer industry. While you can bend a

computer language to your will and force it to perform a task, some tasks naturally work

better with some languages. C# has limitations-some architectural and some as a matter of

convenience. The following sections tell you about the areas where C# isn't necessarily the

best language choice.

Native Executable Development

C# is the language of choice for many types of managed application development, those types

of applications that rely upon the .NET Framework. However, C# can't provide native

executables, those that rely exclusively on the underlying operating system. In fact, the only

way to generate native executables with Visual Studio .NET is by using Visual C++. The lack

of native code development potential means you can't use C# in situations where native

executables are the only answer. The following list provides some ideas on when you should

avoid using C# because of native code development requirements:

• Older versions of Windows

• Drivers and other low-level programming

• Downloadable components

It's especially important to consider your knowledge of the client for application services.

Many existing Windows platforms lack .NET Framework support, which means they can't run

managed applications. Consider the fact that the client would need to download such support

before using your component if you used managed code when a native EXE would work

better.

Older Application Support

Most companies have a wealth of existing code that they can ill afford to move to another

development environment. These older applications might work fine as they are today or

require small tweaks in order to keep pace with current technology. Even if you decide to

build part of the application in a mixed environment (part managed and part unmanaged

code), it's often better to continue using the current language. Continuing with Visual C++ or

Visual Basic makes sense from a developer learning curve and code maintenance perspective

when an application already relies on these products and has nothing to gain from using C#.

However, you should differentiate a local monolithic application from a distributed

application on the Internet. Developing new services for an existing application using C#

could make sense if the service is used for generalized access. For example, a web service that

provides support to a company database for your company and several partners might make a

good candidate for C#.

Older Platform Support

Microsoft has been touting platform independence as the reason to use .NET, yet the .NET

Framework doesn't even run on all Windows platforms yet. As of this writing, there aren't any

plans to port the .NET Framework to older Windows platforms, and the deafening quiet from

更多电子书教程下载请登陆http://down.zzbaike.com/ebook

本站提供的电子书教程均为网上搜集，如果该教程涉及或侵害到您的版权请联系我们。

剩余480页未读，继续阅读

ritchiedzx

粉丝: 0
资源: 1

Visual C# .NET 开发完全指南

Tekla .NET_API实例+帮助文档

.NET MAUI for C# Developers 英文书翻译版

expert_asp.net_web_api_2_for_mvc_developers

Kotlin+for+android+developers中文版翻译_kotlin_android_

Spire.Doc_for_.NET_Pro_Edition_v5.6.zip

ASP.NET_Core_in_Action[Andrew_Lock].pdf

ASP.NET_Maker_2019.0.1破解版

Nios_II_Software_Developers_Handbook

《.NET For Java Developers ：Migrating To C# 》电子书

Professional C#, 3rd Edition_AppC_C# for Java Developers.pdf

最新资源