Chapter I Framework and C# Overview 1 .Content Part 1: NET Framework 1. 2. 3. 4. 5. CLR, FCL, CTS

Chapter I Framework and C# Overview 1 Content Part 1: NET Framework 1. 2. 3. 4. 5. CLR, FCL, CTS Namespace Managed code Garbage collection .NET framework architecture Part 2: C# overview 1. 2. Features IDE 2 PART I .NET FRAMEWORK 3 .NET Framework Net 4.0 .NET 3.5 (Nov-2007) VS.NET 2008 Default: Windows 7 .NET 2.0 (Nov-2005) VS.NET 2005 .NET 3.0 (Nov-2006) Default: Windows Vista, Server 2008 .NET 1.1 (Apr-2003) VS .NET 2003 Default: Server 2003 .NET 1.0 (Feb-2002) 4 What is the .NET framework   The .NET Framework is Microsoft’s latest development platform, and is currently in version 4 Key motivations:  Means of integrating disparate operating systems (Linux, Mac OS,…)  No restriction on the type of applications: .NET...
Nội dung trích xuất từ tài liệu:
Chapter I Framework and C# Overview 1 .Content Part 1: NET Framework 1. 2. 3. 4. 5. CLR, FCL, CTS Chapter I Framework and C# Overview 1 Content Content Part 1: NET Framework CLR, FCL, CTS 1. Namespace 2. Managed code 3. Garbage collection 4. .NET framework architecture 5. Part 2: C# overview Features 1. IDE 2. 2 PART I .NET FRAMEWORK .NET 3 .NET Framework .NET Net 4.0 .NET 3.5 (Nov-2007) .NET VS.NET 2008 Default: Windows 7 .NET 2.0 (Nov-2005) .NET VS.NET 2005 .NET 3.0 (Nov-2006) Default: Windows Vista, Server 2008 .NET 1.1 (Apr-2003) .NET VS .NET 2003 Default: Server 2003 .NET 1.0 NET (Feb-2002) 4 What is the .NET framework What The .NET Framework is Microsoft’s latest  development platform, and is currently in version 4 Key motivations:   Means of integrating disparate operating systems (Linux, Mac OS,…)  No restriction on the type of applications: .NET Framework enables the creation of Windows applications, Web applications, Web services…  Can be used from any language, including C#, C+ +, Visual Basic, JScript, and even older languages such as COBOL 5 What’s in the .NET Framework? What’s .NET Framework consists primarily of a gigantic library of  code that you use from your client languages (such as C#) using object-oriented programming (OOP) techniques. Framework Class Library (FCL) contains thousands of  classes to provide access to Windows API and common functions like String Manipulation, Common Data Structures, IO, Streams, Threads, Security, Network Programming, Windows Programming, Web Programming, Data Access, etc. You can use the classes in FCL in your program just as  you would use any other class. You can even apply inheritance and polymorphism to these classes. 6 Common Type System (CTS) Part of the .NET Framework library defines some  basic types. A type is a representation of data, and specifying  some of the most fundamental of facilitates interoperability between languages using the .NET Framework. This is called the Common Type System (CTS).  Example: CTS defines a type, Int32, an integral data  type of 32 bits (4 bytes) which is mapped by int of C# and Integer of VB.Net 7 Common Language Runtime (CLR) Common .NET Common Language Runtime (CLR), which is  responsible for maintaining the execution of all applications developed using the .NET library. Our programs don't directly communicate with the OS but  go through the CLR 8 Executing an application using the.NET framework framework In order for C# code to execute, it must be converted into a  language that the target operating system understands, known as native code. This conversion is called compiling code, an act that is  performed by a compiler. Under the .NET Framework, this is a two-stage process.  Compile your code into Common Intermediate Language  (CIL) code. JIT compiler (just-in-time) compiles CIL into native code that  is specific to the OS and machine architecture being targeted. 9 IL (Intermediate Language)   MSIL (Microsoft Intermediate Language)  CIL (Common Intermediate Language)  Alternate calling ways of the Intermediate language 10 Assemblies Assemblies When you compile an application, the CIL code  created is stored in an assembly. Assemblies include:   Executable application files (.exe ) and libraries (.dll )  meta information (about the information contained in the assembly) and optional resources (additional data used by the CIL, such as sound files and pictures). 11 Managed Code Managed Code written using the .NET Framework is managed  when it is executed. CLR looks after your applications by managing  memory, handling security, allowing cross-language debugging,.. Applications that do not run under the control of the  CLR are said to be unmanaged In C# you can write only code that runs in a  managed environment. You will make use of the managed features of the CLR and allow .NET itself to handle any interaction with the operating system 12 Garbage Collection Garbage Is the .NET method of making sure that the memory  used by an application is freed up completely when the application is no longer in use. Prior to .NET this was mostly the responsibility of  programmers. .NET garbage collection works by periodically  inspecting the memory of your computer and removing anything from it that is no longer needed. There is no set time frame for this; it might happen  thousands ...