Bonus 2: Handling Files and Libraries in C# CD27 in Visual C#

Creator Code 128 Code Set A in Visual C# Bonus 2: Handling Files and Libraries in C# CD27

Dividing a Single Program into Multiple Source Files CD28 Dividing a Single Program into Multiple Assemblies CD29 Collecting Source Files into Namespaces CD30 Declaring a namespace CD31 Seeing the importance of namespaces CD32 Accessing classes in the same namespace with fully qualified names CD34 Using a namespace CD35 How about using a fully qualified example CD36 Collecting Classes into Class Libraries CD39 Creating a class library project CD39 Creating classes for the library CD40 Creating a driver project CD41

Collecting Data into Files CD43 Using StreamWriter CD45 Improving your reading speed and comprehension through StreamReader CD50

Iterating through a Directory of Files CD55 Writing Your Own Collection Class: The Linked List CD62 An example linked-list container CD63 Why bother with a linked list CD73 Iterating foreach Collections: Iterators CD73 Accessing a collection: The general problem CD74 Letting C# access data foreach container CD76 Accessing Collections the Array Way: Indexers CD77 Indexer format CD78 Example indexer program CD78 Looping around the Iterator Block CD82 Iterating days of the month: A first example CD87 What s a collection, really CD89 Iterator syntax gives up so easily CD90 Iterator blocks of all shapes and sizes CD92 Where to put your iterator CD95

Customizing the Window Layout CD100 Examining the window display states CD100 Hiding a window CD103 Rearranging windows CD103 Stacking windows CD105 More cool nifties, er, productivity tools CD106 Stirring the Solution Explorer CD107 Simplifying life with projects and solutions CD107 Displaying the project CD108 Multisourcing your way to success: Adding a class CD111 Completing the example classes CD112 Converting classes into a program CD115 Considering What Code Should Look Like CD116 Getting Help Quickly! CD120 F1 Help CD120 Index Help CD122 Search Help CD124 More Help goodies CD125 Auto list members Help CD126 De -Debugging Windows CD127 Your program has bugs: It s time to call the exterminator! CD128 Learning the single-step dance CD130 Let me break my point CD134 Operator, trace that call stack! CD137 It s soup CD138

Working Without a Net But Not a NET CD140 Grabbing the free ingredients CD141 Going around the C# development cycle CD142 Doing C# with SharpDevelop CD142 Examining SharpDevelop CD143 Comparing SharpDevelop features with Visual Studio CD144 Getting help CD145 Configuring SharpDevelop CD146 Adding a tool to launch the debugger CD146 Running the debugger from SharpDevelop CD147 Missing debugger stuff CD150 Doing C# with TextPad CD150 Creating a C# CS document class CD153 Adding a tool of your own: Build C# Debug CD155 Configuring a tool to do a Release build CD157 Explaining the configuration options for the Debug and Release tools CD158 Dealing with compiler errors CD162 Configuring the rest of the tools CD162 Testing It with NUnit CD165 Running NUnit CD166 Testing I have to do testing CD166 Writing NUnit tests CD168 Debugging bugs in your test code CD175 Writing Windows Forms Code without a Form Designer CD177 It s just code CD177 Doing it the designer s way CD178 Understanding the new partial classes CD179 Doing it your own way CD180 Making Sure Your Users Can Run Your C# Programs CD180 A Poor Coder s Visual Studio CD180

he C# programming language is a powerful, relatively new descendant of the earlier C, C++, and Java languages Programming with it is a lot of fun, as you re about to find out in this book Microsoft created C# as a major part of its NET initiative For what are probably political reasons, Microsoft turned the specifications for the C# language over to the ECMA (pronounced ek-ma) international standards committee in the summer of 2000, long before NET was a reality In theory, any company can come up with its own version of C# written to run on any operating system, on any machine larger than a calculator When the first edition of this book came out, Microsoft s C# compiler was the only game in town, and its Visual Studio NET suite of tools offered the only way to program C# (other than at the Windows command line) Since then, however, Visual Studio has gone through two major revisions Visual Studio 2003 and, very recently, Visual Studio 2005 And at least two other players have entered the C# game It s now possible to write and compile C# programs on a variety of Unix-based machines using either the Mono or Portable NET implementations of NET and C#: Mono (wwwgo-monocom) is an open-source software project sponsored by Novell Corporation Version 118 came out in June 2005 While Mono lags Microsoft s NET, just now implementing the 11 version that Microsoft released a couple of years ago, it appears to be moving fast Portable NET, under the banner of Southern Storm Software and DotGNU (wwwdotgnuorg/pnethtml), is also open-source Portable NET is at version 070 as of this writing

Both Mono and Portable NET claim to run C# programs on Windows and a variety of Unix flavors, including Linux and Apple s Macintosh operating system At this writing, Portable NET reaches the greater number of flavors, while Mono boasts a more complete NET implementation So choosing between them can be complicated, depending on your project, your platform, and your goals (Books about programming for these platforms are becoming available already Check wwwamazoncom) Open-source software is written by collaborating groups of volunteer programmers and is usually free to the world