Wiley 978-0-470-19137-8 Datasheet

Part IThe C# LanguageChapter 1: .NET ArchitectureChapter 2: C# BasicsChapter 3: Objects and TypesChapter 4: InheritanceChapter 5: ArraysChapter 6: Ope

Part I: The C# Language10 The following table explains the types shown in Figure 1 - 1 . Built-in ValueTypesUser-definedValue TypesValue TypePointer

Chapter 1: .NET Architecture11 We will not list all of the built - in value types here, because they are covered in detail in Chapter

Part I: The C# Language12component can destroy itself and free up associated memory and resources. The problem with this is that it still relies on th

Chapter 1: .NET Architecture13 In pre - .NET days, the choice would be between allowing those instances to share a process (with the resultant risk o

Part I: The C# Language14 Application domains are designed as a way of separating components without resulting in the performance problems associate

Chapter 1: .NET Architecture15 The architecture of exception handling also provides a convenient means to pass an object containing precise details of

Part I: The C# Language16 The fact that an assembly contains program metadata means that applications or other assemblies that call up code in a given

Chapter 1: .NET Architecture17 The solution to these problems is placing shared assemblies in a special directory subtree in the file system, known as

Part I: The C# Language18ensures data types are correctly converted, so the task is no harder than calling the function directly from C++ code would h

Chapter 1: .NET Architecture19This protects, in most situations, the classes in your application from possible name clashes with classes written by ot

c01.indd 2c01.indd 2 2/19/08 4:56:41 PM2/19/08 4:56:41 PM

Part I: The C# Language20 Last, but not least, ASP.NET is remarkable for its increased performance. Whereas classic ASP pages are interpreted with eac

Chapter 1: .NET Architecture21 Creating Windows Forms Although C# and .NET are particularly suited to Web development, they still offer splendid sup

Part I: The C# Language22code for a basic Windows Service. Chapter 23 , “ Windows Services, ” explores how to write C# Windows Services. Windo

Chapter 1: .NET Architecture23just where to look. Because deploying .NET enterprise components involves simply copying files into directories, develop

Part I: The C# Language24 You learned about the characteristics of IL, particularly its strong data typing and object orientation, and how these chara

Part I: The C# Language4 The Relationship of C# to . NET C# is a relatively new programming language and is significant in two respects: ❑ It is

Chapter 1: .NET Architecture5interpreted. One of the disadvantages of Java was that, on execution, the process of translating from Java byte code to n

Part I: The C# Language6you will need to check through the new Visual Basic 2008 code to make sure that the project still works as intended because th

Chapter 1: .NET Architecture7 A Closer Look at Intermediate Language From what you learned in the previous section, Microsoft Intermediate Language

Part I: The C# Language8different languages directly communicate with each other, or instantiate instances of each other — it was always done with C

Chapter 1: .NET Architecture9(as opposed to references) are permitted only in marked blocks of code in C#, and not at all in Visual Basic (although th