Wiley 978-0-470-50225-9 Datenblatt

PART IThe C# LanguageCHAPTER 1: .NET ArchitectureCHAPTER 2: Core C#CHAPTER 3: Objects and TypesCHAPTER 4: InheritanceCHAPTER 5: GenericsCHAPTER 6: Arr

10 ❘ CHAPTER 1 .NET ARCHITECTURE This example shows that the CLS works in two ways. 1. Individual compilers do not have to be powerful eno

ones are accessible from your code — that is, which objects have references that refer to them. Any objects that are not referred to are deemed to b

12 ❘ CHAPTER 1 .NET ARCHITECTURE In general, any process is able to access memory only by specifying an address in virtual memory — processes do n

out - of - bounds array operations are permitted. If a running application does need to communicate or share data with other applications running in d

14 ❘ CHAPTER 1 .NET ARCHITECTURE ASSEMBLIES An assembly is the logical unit that contains compiled code targeted at the .NET Framework. Assembli

is, therefore, less need to take security precautions because there is no risk, for example, of some other commercial software overwriting one of your

16 ❘ CHAPTER 1 .NET ARCHITECTURE .NET FRAMEWORK CLASSES Perhaps one of the biggest benefi ts of writing managed code, at least from a developer ’ s

NAMESPACES Namespaces are the way that .NET avoids name clashes between classes. They are designed to prevent situations in which you defi ne a cl

18 ❘ CHAPTER 1 .NET ARCHITECTUREASP days.) Because you can factor a page ’ s functionality into event handlers with explicit meanings, ASP.NET pages

and proprietary formats such as Electronic Data Interchange (EDI). XML Web services are designed for a service - oriented Web, in which remote compu

c01.indd 2c01.indd 2 5/17/11 6:33:58 PM5/17/11 6:33:58 PM

20 ❘ CHAPTER 1 .NET ARCHITECTURE Windows Services A Windows Service (originally called an NT Service) is a program designed to run in the backgrou

to focus on gluing their data access objects together in methods that accurately enforce their organizations ’ business rules. Moreover, with attribu

22 ❘ CHAPTER 1 .NET ARCHITECTURE JIT compilation Application domains Garbage collection Figure 1 - 4 provides an overview of how these fe

1 .NET Architecture WHAT ’ S IN THIS CHAPTER? Compiling and running code that targets .NET Advantages of Microsoft Intermediate Lan

4 ❘ CHAPTER 1 .NET ARCHITECTURE One important thing to make clear is that C# is a language in its own right. Although it is designed to generate cod

This explains why we can expect that execution of managed IL code will be almost as fast as executing native machine code. What it does not explain i

6 ❘ CHAPTER 1 .NET ARCHITECTUREthat it will run independently of the .NET runtime. If you want your C++ code to run within the .NET Framework, you c

Support for Object Orientation and Interfaces The language independence of .NET does have some practical limitations. IL is inevitably going to imp

8 ❘ CHAPTER 1 .NET ARCHITECTURE This is all quite an ambitious aim, but amazingly, .NET and IL have achieved it. In the case of stepping between met

Suppose that one of the methods of a Visual Basic 2010 class is defi ned to return an Integer — one of the standard data types available in Visual