Chapter 2: Building C# Applications

Add the followingC# andlinetheto the.NETendPlatform,of the currentSecondvalueEdition(note each value in the Path variable is separated

<drive>:\%windir%\MicrosoftThis comprehensive text starts.NET\Framework\v1with brief over iew.1of.4322the C# language and then quickly moves to key technical and

architectural issues for .NET developers.

Table of

C# and the

Introduction

Part One -

Chapter 1

Chapter 2

Part Two

Chapter 3

Figure 2-1: Establishing the path to csc.exe

Chapter 4 - Object-Oriented Programming with C#

Chapter 5 - Exceptions and Object Lifetime

ChapterOf course,6 -theIntexactrf espathndnameCollectionsmay need to be adjusted based on your current version and location of

Chapterthe .NET7 SDK- Callback(so beIntesurfaces,to doDelegates,sanity check)and Events. Once you have added the correct Path setting, you may

Chaptertake a test8 -runAdvanby closinged C# Typeany commandConstructionwindowsTechniquesopen in the background (to commit the settings), then

PartopenThreea new- Prcommandgrammingwindowwith .NETandAssembliesenter:

Part Four - Leveraging the .NET Libraries

If you set things up correctly, you should see a display of each option supported by the raw C# compiler.

Chapter 12 - Object Serialization and the .NET Remoting Layer

Chapter 13 - Building a Better Window (Introducing Windows Forms)

ChapterConfiguring14 - A BetterAdditionalPainting Framework.NET(GDI+)Command Line Tools

Chapter 15 - Programming with Windows Forms Controls

Now, before we begin to investigate manipulating csc.exe, add the following additional Path variable to the

Chapter 16 - The System.IO Namespace

System Variables list box (again, performing a sanity check to ensure path settings):

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter<drive>:\Program18 - ASP.NET WebFiles\MicrosoftPages and Web ControlsVisual Studio .NET\FrameworkSDK\Bin

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

As you will see later in this text, this path contains additional command line tools (such as sn.exe, al.exe,

Index

wsdl.exe and so forth) that are commonly used during .NET development. With these two path settings

established, you should now be able to run any .NET utility directly from the command line. If you wish to

List of Tables

confirm this new setting, close any open command window, open a new command window and enter the following command to view the flags for the assembly linker utility, al.exe:

al -?

Note Now that you have seen how to manually configure your .NET command line tools, I'll let you in on a shortcut. If you own a copy of VS .NET 2003, navigate to the Microsoft Visual Studio .NET 2003 | Visual Studio .NET Tools menu using the Window's Start button. There you will find a preconfigured command prompt (Visual Studio 2003 Command Prompt) that can be used to run

.NET command line tools without the need to manually set your Path settings.

compile TestApp.cs simply by saying:

C# and the .NET Platform, Second Edition

This comprehensive text starts with a brief overview of the

C# language and then quickly moves to key technical and

To try things for yourself, open a command window and change to the directory containing your architectural issues for .NET developers.

TestApp.cs file. Then, enter the previous command and hit return. This builds TestApp.exe, which can now be run from the command line (see Figure 2-2).

Table of Contents

C# and

Part

Chapter

Chapter

Part

Chapter

Chapter

Figure 2-2: The TestApp in action

Chapter 5 - Exceptions and Object Lifetime

Chapter 6 - Interfaces and Collections

The first thing that should strike you is the fact that you have just created a console application using C#!

Chapter 7 - Callback Interfaces, Delegates, and Events

The reason I point this out is due to a common misconception (especially among management) that .NET

Chapter 8 - Advanced C# Type Construction Techniques

is only useful during the development of Internet applications. Nothing could be further from the truth. As PartyouThreewill see- Programmingover the coursewithof.NETthisAssembliestext, .NET provides support for developing any type of application you

Chaptermight envision9 - U derstanding(Web-based.NETor otherwise)Assemblies.

Chapter 10 - Processes, AppDomains, Contexts, and Threads

While console applications are far less sexy than a Windows-based or HTML-based front end, they can

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

prove useful when you need to build a program that requires a minimal graphical user interface.

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer

Note Given their simplicity, the initial chapters of this text make use of simple command window

Chapter 13 - Building a Better Window (Introducing Windows Forms)

applications to ensure that you are able to focus on the syntax of C# rather than focusing on the

Chapter 14 - A Better Painting Framework (GDI+)

complexities of building GUIs using Windows Forms or ASP.NET technologies.

Chapter 15 - Programming with Windows Forms Controls

Chapter 16 - The System.IO Namespace

Referencing External Assemblies

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Next up, let's examine how to build an application that makes use of types defined in a separate .NET

Chapter 18 - ASP.NET Web Pages and Web Controls

assembly. Speaking of which, just in case you are wondering how the C# compiler understood your

Chapter 19 - ASP.NET Web Applications

reference to the System.Console type, realize that mscorlib.dll is automatically referenced during the

Chapter 20 - XML Web Services

compilation process (if for some strange reason you wish to disable this behavior, you may specify the Index/nostdlib flag).

List of Figures

To illustrate the process of referencing external assemblies, let's update the TestApp application to display

List of Tables

a Windows Forms message box. Thus, open your TestApp.cs file and modify it as follows:

using System;

// Add this!

using System.Windows.Forms; class TestApp

{

public static void Main()

{

Console.WriteLine("Testing! 1, 2, 3");

// Add this!

MessageBox.Show("Hello...");

}

}

Notice the reference to the System.Windows.Forms namespace (via the C# "using" directive introduced in

C# and the .NET Platform, Second Edition

Chapter 1). Recall that when you explicitly list the namespaces used within a given *.cs file, you avoid the

by Andrew Troelsen ISBN:1590590554 need to make use of fully qualified names (which can lead to hand cramps).

Apress © 2003 (1200 pages)

In addition to usingThisthecomprehensive"using" keyword,textyoustartsmustwi halsoa briefinformoverviewcsc.exeof thewhich assembly contains the

C# language and then quickly moves to key technical and

referenced namespace. Given that we have made use of the System.Windows.FormsMessageBox class,

architectural issues for .NET developers.

you must specify the System.Windows.Forms.dll assembly using the /reference flag (which can be abbreviated to /r):

Table of Contents

csc /r:System.Windows.Forms.dll testapp.cs

C# and the .NET Platform, Second Edition

Introduction

Part One - Introducing C# and the .NET Platform

If you now rerun your application, you should see what appears in Figure 2-3.

Chapter 1 - The Philosophy of .NET

Chapter 2 - Building C# Applications

Figure 2-3: Your first Windows Forms application

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Compiling Multiple Source Files

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer

The current incarnation of the TestApp.exe application was created using a single *.cs source code file (as

Chapter 13 - Building a Better Window (Introducing Windows Forms)

well as a single external assembly). While it is perfectly permissible to have all of your .NET types defined

Chapter 14 - A Better Painting Framework (GDI+)

in a single *.cs file, most projects are composed of multiple *.cs files to keep your code base a bit more

Chapter 15 - Programming with Windows Forms Controls

flexible. To illustrate, assume you have authored an additional class contained in a new file named

Chapter 16 - The System.IO Namespace

HelloMsg.cs.

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

// The HelloMessage Class

Chapter 18 - ASP.NET Web Pages and Web Controls

using System;

Chapter 19 - ASP.NET Web Applications

using System.Windows.Forms;

Chapter 20 - XML Web Services

class HelloMessage

Index

{

List of Figures

public void Speak()

List of Tables{ MessageBox.Show("Hello..."); }

}

Now, update your initial TestApp class to make use of this new type, and comment out the previous Windows Forms logic:

using System;

//Don't need this anymore.

//using System.Windows.Forms;

class TestApp

{

public static void Main()

{

Console.WriteLine("Testing! 1, 2, 3");

// Don't need this anymore either.

}

Table of Contents

You can compile this multifile application by listing each *.cs file explicitly:

C# and the .NET Platform, Second Edition

Introduction

csc /r:System.Windows.Forms.dll testapp.cs hellomsg.cs

Part One - Introducing C# and the .NET Platform

Chapter 1 - The Philosophy of .NET

Chapter 2 - Building C# Applications

Part Two - The C# Programming Language

As an alternative, the C# compiler allows you to make use of the wildcard character (*) to inform csc.exe

Chapter 3 - C# Language Fundamentals

to include all *.cs files contained in the project directory as part of the current build. When you use this Chapteroption,4you- willObjecttypically-OrientedwantPrtogrammingspecify thewithnameC# of the output file (/out) as well, to directly control the

Chnamept rof5 the- Excepresultingonsassembly:and O ject Lifetime

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

csc /r:System.Windows.Forms.dll /out:TestApp.exe *.cs

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

When you run the program again, the output is identical. The only difference between the two applications

Chapter 9 - Understanding .NET Assemblies

is the fact that the current logic has been split among multiple files.

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

PartReferencingFour - LeveragingMultiplethe .NET LibrariesExternal Assemblies

Chapter 12 - Object Serialization and the .NET Remoting Layer

Now, what if you need to reference numerous external assemblies? Simply list each assembly using a

Chapter 13 - Buildi g a Better Window (Introducing Wi dows Forms)

semicolon-delimited list (annoyingly, the VB .NET compiler [vbc.exe] uses a comma delimited list, so be

Chapter 14 - A Better Painting Framework (GDI+)

mindful when using multiple .NET compilers). You don't need to specify multiple external assemblies for

Chapter 15 - Programming with Windows Forms Controls

the current example, but some sample usage follows:

Chapter 16 - The System.IO Namespace Chapter 17 - Data Access with ADO.NET

csc /r:System.Windows.Forms.dll;System.Drawing.dll /out:TestApp.exe *.cs

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

Working withC# andCscthe.exe.NET ResponsePlatform, SecondFilesEdition

As you might guess, if you were to build a complex C# application at the command prompt, your life would

Apress © 2003 (1200 pages)

be full of pain as you type in the flags that specify numerous referenced assemblies and *.cs input files. To

This comprehensive text starts with a brief overview of the

help lessen your C#typinglanguageburden,andthethenC#quicklycompilermoveshonorsto keythetechnicaluse of "responseand files."

architectural issues for .NET developers.

C# response files contain all the instructions to be used during the compilation of your current build. By convention, these files end in a *.rsp (response) extension and can be used as an alternative to pounding

Tableout linesof Contentsand lines of flags manually at the command prompt. To illustrate, assume that you have created C#a responseand the .NETfile Plnamedtform,TestAppSecond.rspEditionthat contains the following arguments (as you can see, comments are

denoted with the "#" character):

Introduction

Part One - Introducing C# and the .NET Platform

Chapter# This1 is- ThethePhilosophyresponseof .NETfile

Chapter# for2the- BuildingTestAppC# .Applicationsexe app

Part# ofTwoChapter- The C# Programming2. Language

Chapter# External3 - C# assemblyLanguage Fundamentalsreferences.

/r:System.Windows.Forms.dll

Chapter 4 - Object-Oriented Programming with C#

# output and files to compile (using wildcard syntax).

Chapter 5 - Exceptions and Object Lifetime

/target:exe /out:TestApp.exe *.cs

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Now, assuming this file is saved in the same directory as the C# source code files to be compiled, you are

Part Three - Programming with .NET Assemblies

able to build your entire application as follows (note the use of the @ symbol):

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

csc@TestApp.rsp

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer

Chapter 13 - Building a Better Window (Introducing Windows Forms)

Again, the output of the compiler is identical.

Chapter 14 - A Better Painting Framework (GDI+)

If the need should arise, you are also able to specify multiple *.rsp files as input (for example: csc

Chapter 15 - Programming with Windows Forms Controls

@FirstFile.rsp @SecondFile.rsp @ThirdFile.rsp). If you take this approach, do be aware that the compiler

Chapter 16 - The System.IO Namespace

processes the command options as they are encountered! Therefore, command line arguments in a later

Chapter 17 - Data Access with ADO.NET

*.rsp file can override options in a previous response file.

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Also note that any flags listed explicitly on the command line will be overridden by the options in a given

Chapter 19 - ASP.NET Web Applications response file. Thus, if you were to enter:

Chapter 20 - XML Web Services

Index

csc/out:Foo.exe @TestApp.rsp

List of Figures

List of Tables

the name of the assembly would still be TestApp.exe (rather than Foo.exe), given the /out:TestApp.exe flag listed in the TestApp.rsp response file.

The Default Response File (csc.rsp)

The final point to be made regarding response files is that the C# compiler has an associated default response file (csc.rsp), which is located in the same directory as csc.exe itself. If you were to open this file using Notepad, you will find that numerous .NET assemblies have already been specified using the /r: flag (Figure 2-4).

ISBN:1590590554

of the

and

Table

C# and

Part

Chapter

Chapter

Part

Chapter

Chapter

Chapter

ChapterFigure6 - 2Interfaces-4: Behold,andtheColldefaultctionsresponse file

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

When you are building your C# programs using csc.exe, this file will be automatically referenced, even

Part Three - Programming with .NET Assemblies

when you supply a custom *.rsp file (be aware that Visual Studio .NET does not make use of response

Chapter 9 - Understanding .NET Assemblies

files whatsoever, custom or csc.rsp). Given the presence of the default response file, it should be clear

Chapter 10 - Processes, AppDomains, Contexts, and Threads

that the current TestApp.exe application (which contains a reference to the

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

System.Windows.Forms.MessageBox class) could be successfully compiled using the following command

Part Four - Leveraging the .NET Libraries

line (note that I did not specify /r:System.Windows.Forms.dll as this reference will be added via csc.rsp):

Chapter 12 - Object Serialization and the .NET Remoting Layer

Chapter 13 - Building a Better Window (Introducing Windows Forms) csc /out:TestApp.exe *.cs

Chapter 14 - A Better Painting Framework (GDI+) Chapter 15 - Programming with Windows Forms Controls

ChapterFinally,16in the- TheeventSystemthat.IOyouNamespacewish to disable the automatic reading of csc.rsp, you can specify the /noconfig

Chflag:pter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

csc @TestApp.rsp /noconfig

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

GeneratingC#Bugand theReports.NET Platform, Second Edition

The raw C# compiler provides a helpful flag named /bugreport. As you can gather by its name, this flag

Apress © 2003 (1200 pages)

allows you to specify a file that will be populated (by csc.exe) with various statistics regarding your current

This comprehensive text starts with a brief overview of the

build; including anyC#errorslanguageencounteredand hen quicklyduringmovesthe compilationto key technicalprocessand. Its use is self-explanatory:

architectural issues for .NET developers.

csc/bugreport:bugs.txt *.cs

Table of Contents

C# and the .NET Platform, Second Edition

When you specify /bugreport, you will be prompted to enter corrective information for the possible error(s)

Introduction

at hand, which will be saved (along with other details) into the file you specify. To illustrate, let's inject a

PartbugOintoe -theIntroducingTestApp C#class:and the .NET Platform

Chapter 1 - The Philosophy of .NET

Chapter 2 - Building C# Applications

public static void Main()

Part Two - The C# Programming Language

{

Chapter 3 - C# Language Fundamentals

...

Chapter 4 - Object-Oriented Programming with C#

HelloMessage h = new HelloMessage();

Chapter 5 - Exceptions and Object Lifetime

// Note lack of semicolon below!

Chapterh.Speak()6 - Interfaces//and<=CollectionsError!

Chapter} 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

When you recompile this file using the /bugreport flag, you are prompted to enter corrective action for the

Chapter 9 - Understanding .NET Assemblies

error at hand (Figure 2-5).

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part

Chapter

Chapter

Chapter

Chapter

Chapter

Chapter

Part

Chapter

Chapter

Chapter

IndexFigure 2-5: Documenting the bug

List of Figures

List of Tables

If you were to open the resulting *.txt file you would find a complete report regarding this compilation cycle (Figure 2-6).

ISBN:1590590554

overview of the technical and

Table

C# and

Part

Chapter

Figure 2-6: The entire bug report

Chapter 2 - Building C# Applications

Part Two - The C# Programming Language

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

Chapter 5 - Exceptions and Object Lifetime

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer Chapter 13 - Building a Better Window (Introducing Windows Forms) Chapter 14 - A Better Painting Framework (GDI+)

Chapter 15 - Programming with Windows Forms Controls

Chapter 16 - The System.IO Namespace

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

RemainingC#C#andCompilerthe .NET Platform,OptionsSecond Edition

Obviously, the C# compiler has many other flags that can be used to control how the resulting .NET

Apress © 2003 (1200 pages)

assembly is to be generated. For example, flags exist to build XML source code documentation files

This comprehensive text starts with a brief overview of the

(explained shortly),C#createlanguagemultifileand thenassemblies,quickly movesand embedto k y technical.NET resourceand files. Although I will comment on additional commandarchitecturalline flagsissueswherefor .NETnecessarydevelopersduring. the remainder of this text, Table 2-2 documents the complete set of possible flags (listed alphabetically).

Chapter 1 - The Philosophy of .NET

CODE

Chapter 2 - Building C# Applications

Part Two - The C# Programming Language

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

Chapter 5 - Exceptions and Object Lifetime

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer

Chapter 13 - Building a Better Window (Introducing Windows Forms)

Chapter 14 - A Better Painting Framework (GDI+)

Chapter 15 - Programming with Windows Forms Controls

Chapter 16 - The System.IO Namespace

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

At this point, you are in debugging mode, and may apply any number of cordbg.exe flags at the "(cordbg)"

C# and the .NET Platform, Second Edition command prompt (Figure 2-7).

Apress © 2003 (1200 pages)

of the

and

Table

C# and

Part

Chapter

Chapter

Part Two - The C# Programming Language

Figure 2-7: Debugging at the command line

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

ChapterWhen you5 -areExceptionsfinishedanddebuggingObject Lifetimeyour application and wish to exit debugging mode, simply type exit (or Chapterthe shorthand6 - Interfaces"ex"). Again,and Collectionsunless you are a command-line warrior, I assume you will opt for the integrated

VS .NET IDE debugger. If you are interested in further details of cordbg.exe, check out online Help.

Chapter 7 - Callback Interfaces, D legates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer

Chapter 13 - Building a Better Window (Introducing Windows Forms)

Chapter 14 - A Better Painting Framework (GDI+)

Chapter 15 - Programming with Windows Forms Controls

Chapter 16 - The System.IO Namespace

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

Using the VisualC# and theStudio.NET Platform,.NET SecondIDE Edition

Now that you have had the chance to work with the C# compiler in the raw, we can turn our attention to the

Apress © 2003 (1200 pages)

use of Visual Studio .NET. As mentioned, this product allows you to build applications using any number of

This comprehensive text starts with a brief overview of the

.NET-aware (andC#unaware)languagelanguagesand then .quicklyThus, movesyou aretoablekey totechnicaluse VSand.NET when building C#, J#, VB

.NET, MFC, ATLarchitectural(4.0) or traditionalissues Cfor-based.NET developersWin32 applications. . The one thing you cannot do is build a traditional Visual Basic 6.0 application using VS .NET. If you want to create classic VB 6.0 COM servers (or any additional VB 6.0 project types) you need to make use of the Visual Basic 6.0 IDE (and yes, it is safe to

Table of Contents

have both IDEs installed on a single development machine).

C# and the .NET Platform, Second Edition

Let's take some time to examine the core features of the Visual Studio .NET IDE (the operative word being

Introduction

core). My goal in this section is not to comment on each and every option of the IDE's menu system,

Part One - Introducing C# and the .NET Platform

document each of the integrated wizards, or offer exhaustive details for a given GUI configuration tool. I

Chapter 1 - The Philosophy of .NET

assume that you are more than capable of examining the IDE at your leisure. Nevertheless, let's check out

Chapter 2 - Building C# Applications

some key traits you will tend to use on a daily basis (and of course, other key aspects of the development

Part Two - The C# Programming Language

environment will be pointed out as necessary throughout this text).

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

ChaptTherVS5 - .ExceptionsNET Startand ObjectPageLifetime

Chapter 6 - Interfaces and Collections

By default, the first thing you see when you launch Visual Studio .NET is the Start Page. For the present,

Chapter 7 - Callback Interfaces, Delegates, and Events

you need only be concerned with the Projects and My Profile tabs (the remaining options allow you to

Chapter 8 - Advanced C# Type Construction Techniques

connect to the Internet to view online resources, obtain product updates, and whatnot).

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

The Projects view (Figure 2-8) allows you to open existing projects as well as create a brand-new project

Chapter 10 - Processes, AppDomains, Contexts, and Threads

workspace. Be aware that these options are also available via the File menu.

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Index

Figure 2-8: The Projects tab of the VS .NET Start Page

List of Figures

List of Tables

Now, if you were to click the My Profile tab, you would be shown something like what you see in Figure 2- 9.

Second Edition

ISBN:1590590554

with a brief overview of the

moves to key technical and

developers.

Table

C# and

Part

Chapter

Chapter

Part Two - The C# Programming Language

Figure 2-9: The My Profile tab of the VS .NET Start Page

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

Here, you are able to control how the VS .NET IDE should be configured each time you launch the tool.

Chapter 5 - Exceptions and Object Lifetime

For example, the Keyboard Scheme drop-down list allows you to control which keyboard mapping should

Chapter 6 - Interfaces and Collections

be used. If you want, you can opt to have your shortcut keys configured to mimic VB 6.0, Visual C++ 6.0,

Chapter 7 - Callback Interfaces, Delegates, and Events or the default VS .NET settings.

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

Other options allow you to configure how online Help should be filtered (and displayed), as well as how the

Chapter 9 - UnderstandingProperties,.NET A semblies

core IDE windows (i.e., Toolbox, etc.) should dock themselves. To check things out first-hand, Chaptertake a moment10 - Procesto selects, AppDomathe variousns, Contexts,options foundand Threadsunder the Window Layout drop-down list and find a look

Chapterand feel11you- Typeare comfortableReflection, LatewithBinding,. and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Finally, be aware that if you close the Start Page window (and want to get it back), access the Help | Show

Chapter 12 - Object Serialization and the .NET Remoting Layer

Start Page menu option. On a related note, if you do not want to see the Start Page, you can disable its

Chapter 13 - Building a Better Window (Introducing Windows Forms)

automatic display using the At Startup drop-down list from the My Profile section.

Chapter 14 - A Better Painting Framework (GDI+)

Chapter 15 - Programming with Windows Forms Controls

ChaptCreatingr 16 - TheaSystemVS .NET.IO NamespaceProject Solution

Chapter 17 - Data Access with ADO.NET

Our next stop on the tour is to get to know the various types of C# project workspaces. Open the New

Part Five - Web Applications and XML Web Services

Project dialog box by clicking the New Project button from the Start Page, or by choosing the File | New |

Chapter 18 - ASP.NET Web Pages and Web Controls

Project menu selection. As you can see from Figure 2-10, project types are grouped (more or less) by language (do note that you may not have each of the .NET-aware languages, or project options shown in

Figure 2-10, based on your edition of VS .NET and/or the managed languages installed on your

Index

development machine).

List of Figures

List of Tables

ISBN:1590590554

of the

and

Table

C# and

Part

Chapter

Chapter

Part

Chapter 3 - C# Language Fundamentals

Figure 2-10: The New Project dialog box

Chapter 4 - Object-Oriented Programming with C#

Table 2-4 offers an explanation of the core C# project types (again, note that other project workspaces are

Chapter 5 - Exceptions and Object Lifetime

possible based on the installation of optional .NET SDKs and your version of VS .NET).

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

Table 2-4: Core Project Workspace Types

Chapter 8 - Advanced C# Type Construction Techniques

ChapterASP.NET17 - WebData AccessSelectwith ADOthis option.NET when you want to build an ASP.NET Web application.

PartApplicationFive - Web Applications and XML Web Services

Note In addition to the items listed in Table 2-4, be aware that VS .NET 2003 also defines a number of project types that target mobile .NET development (previously only available using freely downloadable plug-ins).

Building a VSC# and.NETthe .NETTestPlatform,ApplicationSecond Edition

To illustrate the basic mechanics of this new IDE, let's build a new console application that mimics the

Apress © 2003 (1200 pages)

functionality of the previous TestApp.exe assembly. To get started, create a brand-new C# Console

This comprehensive text starts with a brief overview of the

Application projectC#namedlanguageVsTestAppand then.quicklyOnce youmoveshit OK,to keyyoutechnicalwill findanda new folder has been created that contains a numbera chitecturalof starter filesissuesandforproject.NET developsubdirectoriesrs. . Table 2-5 describes the key items:

Table 2-5: The Structure of a VS .NET Console Application

references, and resources that constitute the application as a whole. Do be aware that regardless of which

Indexproject workspace type you create, the *.sln file can be opened using VS .NET to load each project in the

Listworkspaceof Figur .sUsing the Solution Explorer window, you are able to view and open any such item (Figure 2-

List11)of. NoticeTables the default name of your initial class is "Class1.cs."

Edition

ISBN:1590590554

overview of the

key technical and

Table

C# and

Part

Chapter

Chapter

Part

ChapterFigure3 - 2C#-11:LanguageThe SolutionFundamentalsExplorer

Chapter 4 - Object-Oriented Programming with C#

Chapter 5 - Exceptions and Object Lifetime

Notice as well that the Solution Explorer window provides a Class View tab, which shows the object-

Chapter 6 - Interfaces and Collections

oriented view of your project (Figure 2-12). One nice feature of this perspective is that if you double click

Part

Chapter

Chapter

Chapter

Chapter

Chapter

Chapter

Part

Chapter

Chapter

Chapter

Index

List of

List of

Figure 2-12: Class View

As you would expect, when you right-click a given item, you activate a context-sensitive pop-up menu. The menu lets you access a number of tools that allow you to configure the current project settings and sort items in a variety of ways. For example, right-click the Solution node from Class View and check out Figure 2-13.

ISBN:1590590554

of the and

Table

C# and

Part

Chapter 1 - The Philosophy of .NET

Figure 2-18: Collapsing the SayHi() method

Chapter 2 - Building C# Applications

Part Two - The C# Programming Language

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

Chapter 5 - Exceptions and Object Lifetime

Chapter 6 - Interfaces and Collections

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter 8 - Advanced C# Type Construction Techniques

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

Part Four - Leveraging the .NET Libraries

Chapter 12 - Object Serialization and the .NET Remoting Layer Chapter 13 - Building a Better Window (Introducing Windows Forms) Chapter 14 - A Better Painting Framework (GDI+)

Chapter 15 - Programming with Windows Forms Controls

Chapter 16 - The System.IO Namespace

Chapter 17 - Data Access with ADO.NET

Part Five - Web Applications and XML Web Services

Chapter 18 - ASP.NET Web Pages and Web Controls

Chapter 19 - ASP.NET Web Applications

Chapter 20 - XML Web Services

Index

List of Figures

List of Tables

DebuggingC#withand thehe .NETVisualPlatform,StudioSecond.NETEditionIDE

As you would expect, Visual Studio .NET contains an integrated debugger, which provides the same

Apress © 2003 (1200 pages)

functionality of cordbg.exe using a friendly user interface. To illustrate the basics, begin by clicking in the

This comprehensive text starts with a brief overview of the

far left gray columnC#oflanguan activege andcodeth nwindowquickly tomovesinserttoakeybreakpointtechn cal(Figureand 2-19).

architectural issues for .NET developers.

Table

C# and

Part

Chapter

Chapter

Part

Chapter

Chapter

Chapter

Chapter

Chapter

Chapter

Figure 2-19: Setting breakpoints

Part Three - Programming with .NET Assemblies

Chapter 9 - Understanding .NET Assemblies

ChapterWhen you10 -initiateProc sses,a debugAppDomains,session (viaContexts,the Debugand Threads| Start menu selection), the flow of execution halts at

Cheachpterbreakpoint11 - Type.Reflection,Using the DebugLate Binding,toolbarand(orAttributethe corresponding-Based Programmingkeystroke commands), you can step

Partover,Fourstep- Leverinto, andgingsteptheout.NETofLibrariesgiven function. As you would expect, the integrated debugger hosts a Chapternumber12of-debugO ject-centricSerializationwindowsand(ethe.g..,NETCallRemotingStack, Autos,LayerLocals, Breakpoints, Modules, Exceptions, and

so forth). To show or hide a particular window, simply access the Debug | Windows menu selection while

Chapter 13 - Building a Better Window (Introducing Windows Forms)

in a debugging session.

Chapter 14 - A Better Painting Framework (GDI+) Chapter 15 - Programming with Windows Forms Controls Chapter"Running"16 - The SystVersusm.IO Namespace"Debugging"

Chapter 17 - Data Access with ADO.NET

One VS .NET debugging-related topic has to do with the distinction between running an application (via the

Part Five - Web Applications and XML Web Services

Debug | Start Without Debugging menu selection) verses debugging an application (via the Debug | Start

Chapter 18 - ASP.NET Web Pages and Web Controls

menu selection). When you run an application, you are instructing VS .NET to ignore all breakpoints, and

Chapter 19 - ASP.NET Web Applications

most important, to automatically prompt for a keystroke before terminating the current console window.

Chapter 20 - XML Web Services

Index

On the other hand, if you debug a project that does not have any breakpoints set, the console application

List of Figures

terminates so quickly that you will be unable to view the output! To ensure that the command window is

List of Tables

alive regardless of the presence of a given breakpoint, one surefire technique is to simply add the following code at the end of the Main() method:

static void Main(string[] args)

{

...

// Keep console window up until user hits return.

Console.ReadLine();

}

SOURCE The VsTestApp project is included under the Chapter 2 subdirectory.

CODE

Other Key AspectsC# and the .NETof thePlatform,VS .SecondNET IDEEdition

At this point, you should have a better feeling about the core features of the IDE. I'll assume you will keep

Apress © 2003 (1200 pages)

exploring with the IDE as you read through the book. However, to paint a more complete picture, let's

This comprehensive text starts with a brief overview of the quickly check outC#additionallangu gefeaturesand thenofquicklyVS .NETmoves. to key technical and

architectural issues for .NET developers.

Examining the Server Explorer Window

Table of Contents

One extremely useful aspect of Visual Studio .NET is the Server Explorer window (Figure 2-20), which can

IndexThis window can be thought of as the command center of a distributed application you may be building. ListUsingof Figuresthe Server Explorer, you can attach to and manipulate local and remote databases (and view any of

the given database objects), examine the contents of a given message queue, and obtain general

List of Tables

machine-wide information (such as seeing what services are running and viewing information in the Windows event log). You will see this view of the IDE in action at various places in the text.

XML-Related Editing Tools

Visual Studio .NET also provides numerous XML-related editors. As a simple example, if you insert a new XML file into your application (via the Project | Add New Item... menu selection), you are able to manipulate the underlying XML using GUI design-time tools (and related toolbars). Figure 2-21 shows an XML file you will generate during our discussion of ADO.NET.

ISBN:1590590554

overview of the

technical and

Table

C# and

Part

ChapterFigure1 - 2The-21:PhilosophyThe integratedof .NETXML editor

Chapter 2 - Building C# Applications

Part Two - The C# Programming Language

ChaptTherObject3 - C# LanguageBrowserFundamentalsUtility

Chapter 4 - Object-Oriented Programming with C#

In addition to the type browsing tools you examined in Chapter 1 (such as ildasm.exe and wincv.exe), the

Chapter 5 - Exceptions and Object Lifetime

Visual Studio .NET IDE also supplies a utility that looks and feels much like the VB 6.0/J++ 6.0 Object

Chapter 6 - Interfaces and Collections

Browser. If you access the View | Object Browser menu option, you will see the tool displayed in Figure 2-

Chapter 7 - Callback Interfaces, Delegates, and Events

Chapter

Part

Chapter

ChapterFigure19 - 2ASP-22:.NETTheWebintegratedApplicationsObject Browser

Chapter 20 - XML Web Services

Obviously, the object browser allows you to view the namespaces, types, and type members of each

Index

assembly referenced by the current solution.

List of Figures

List of Tables

Database Manipulation Tools

Integrated database support is also part of the VS .NET IDE. Using the Server Explorer window, you can open and examine any database object from within the IDE. For example, Figure 2-23 shows a view of the Inventory table of the Cars database you build during our examination of ADO.NET.

Figure 2-23: Integrated database editors

Apress © 2003 (1200 pages)

Integrated Help

This comprehensive text starts with a brief overview of the

C# language and then quickly moves to key technical and

The final aspect of the IDE you must be comfortable with from the outset is the fully integrated Help architectural issues for .NET developers.

system. The .NET documentation is extremely good, very readable, and full of useful information. Given the huge number of predefined .NET types (which number well into the thousands) you must be willing to

roll up your sleeves and dig into the provided documentation. If you resist, you are doomed to a long,

Table of Contents

frustrating, and painful existence.

C# and the .NET Platform, Second Edition

Introduction

To prevent this from happening, VS .NET provides the Dynamic Help window, which changes its contents

Part One - Introducing C# and the .NET Platform

(dynamically!) based on what item (window, menu, source code keyword, etc.) is currently selected. For

Chapter 1 - The Philosophy of .NET

example, if you place the cursor on Main() method, the Dynamic Help window displays what's shown in

Chapter 2 - Building C# Applications

Figure 2-24.

Part Two - The C# Programming Language

Chapter 3 - C# Language Fundamentals

Chapter

Chapter

Chapter

Chapter

Chapter

Part

Chapter

Chapter

Part

Chapter

Chapter

Chapter

Chapter

Chapter

Chapter

Part

Chapter

Chapter

Chapter

IndexFigure 2-24: Visual Studio .NET Integrated Help

List of Figures

List of Tables

As you would expect, if you select on one of the suggested links (such as /main), you are shown the information that appears in Figure 2-25.

ISBN:1590590554

of the

and

Table

C# and

Part

Chapter

Chapter

Figure 2-25: Remember, F1 is your friend.

Part Two - The C# Programming Language

Chapter 3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C#

Bookmark This Help Link!

Chapter 5 - Exceptions and Object Lifetime

ChapterIn addition6 -toInterfacescontext-sensitiveand Collectioonlines Help, you should also be aware of a very important subdirectory of

Chapterthe .NET7 MSDN- CallbackHelpInterfaces,system. IfDelegates,you look undera Eventsthe MSDN Library | .NET Development | .NET Framework

ChapterSDK | .8NET- AdvancedFrameworkC#|TypeReferenceConstruction| ClassTechniquesLibrary node of the MSDN library, you will find complete

PartdocumentationThr - Programmingof each andwithevery.NETnamespaceAssemblies in the .NET base class libraries (Figure 2-26). Do be aware Chapterthat the9location- Understandingof the Class.NETLibraryAssembliesnode is subject to change in future (or previous) editions of MSDN.

Chapter 10 - Processes, AppDomains, Contexts, and Threads

Figure 2-26: Again, F1 is your friend.

As you would guess, each "book" defines the set of types in a given namespace, the members of a given type, and the parameters of a given member. Furthermore, when you view the Help page for a given type, you will be told the name of the assembly and namespace that contains the type in question (located at the end of said page). As you read the remainder of this book, I assume that you will dive into this very, very critical node to read up on additional details of the entity under examination.

DocumentingC# andYourthe .SourceNET Platform,CodeSecondviaEditionXML

The next goal of this chapter is to examine a technique honored by the C# compiler, which allows you to

Apress © 2003 (1200 pages)

turn your source code documentation into a corresponding XML file. If you have a background in Java, you

This comprehensive text starts with a brief overview of the

are most likely familiarC# languagewith theandjavadocthen qutilityickly. movesUsing javadoc,to key technicalyou areandable to turn Java source code into a corresponding HTMLarchitecturalrepresentationissues for. The.NETC#developersdocumentation. model is slightly different, in that the "code comments to XML" conversion process is the job of the C# compiler (csc.exe) rather than a stand-alone utility.

Table of Contents

C#So,andwhytheuse.NETXMLPlatoform,documentSecondourEditypeion definitions rather than HTML? The main reason is that XML is a

very enabling technology. Given that XML separates the definition of data from the presentation of that

Introduction

data, we (as programmers) can apply any number of XML transformations to the raw XML. You could also

Part One - Introducing C# and the .NET Platform

programmatically read (and modify) the raw XML using types defined in the System.Xml.dll assembly.

Chapter 1 - The Philosophy of .NET

Chapter 2 - Building C# Applications

When you wish to document your types in XML, your first step is to make use of a special comment syntax,

Part Two - The C# Programming Language

the triple forward slash (///) rather than the C++ style double slash (//) or C-based comment syntax (/*... */).

Chapter 9 - Understanding .NET Assemblies

<c> Indicates that text within a description should be

Chapter 10 - Processes, AppDomains, Contexts, and Threads marked as code

Chapter 11 - Type Reflection, Late Binding, and Attribute-Based Programming

As a concrete example, here is a very streamlined definition of a type named Car, adorned with some XML-based code comments (note the use of the <summary> and <param> tags):

/// <summary>

/// <summary>

/// Do you have a sunroof?

/// </summary>

Table of Contents

private bool hasSunroof = false;

C# and the .NET Platform, Second Edition

Introduction

/// <summary>

Part One - Introducing C# and the .NET Platform

/// The ctor lets you set the sunroofedness.

Chapter 1 - The Philosophy of .NET

/// </summary>

Chapter 2 - Building C# Applications

/// <param name="hasSunroof"> </param>

Part Two - The C# Programming Language

public Car(bool hasSunroof)

Chapter{3 - C# Language Fundamentals

Chapter 4 - Object-Oriented Programming with C# this.hasSunroof = hasSunroof;

Chapter}5 - Exceptions and Object Lifetime

Chapter 6 - Interfaces and Collections

Chapter///7 -<summary>Callback Interfaces, Delegates, and Events

Chapter///8 -ThisAdvancedmethodC# TypeallowsC nstructionyou toTechniquesopen your sunroof.

Part Three///- Progra</summary>ming with .NET Assemblies