.Net Framwork Architecture And components
- 1. A Ray Of Hope PK Irru Pychukar Chukar , Baramulla Jammu And Kashmir BCA | G.D.C Boys Baramulla M.Sc IT | Desh Bhagat University .NET FramWork And Architecture +91 9596 296 421
- 2. NET Framework Basic Architecture And Component Stack Common Language Runtime (CLR) Common Language Specification (CLS) Common Type System (CTS) Garbage Collection (GC) Just In – Time Compiler (JIT) .NET Framwork And Components
- 3. NET Framework Definition: A programming infrastructure created by Microsoft for building, deploying, and running applications and services that use .NET technologies, such as desktop applications and Web services. The .Net framework is a software development platform developed by Microsoft. The framework was meant to create applications, which would run on the Windows Platform. It is used to develop Form-based applications, Web-based applications and Web services. There is a variety of programming languages available on the .Net platform, VB.Net and C# being the most common ones are . It is used to build applications for Windows, phone, web etc. It provides a lot of functionalities and also supports industry standards.
- 4. .Net Framework Architecture The basic architecture of the .Net framework is as shown below.
- 5. Architecture
- 6. Common Language Runtime (CLR) CLR is the basic and Virtual Machine component of the .NET Framework. It is the run-time enviornment in the .NET Framework that runs the codes and helps in making the development process easier by providing the various services. Basically, it is responsible for managing the execution of .NET programs regardless of any .NET programming language. Internally, CLR implements the VES(Virtual Execution System) which is defined in the Microsoft’s implementation of the CLI(Common Language Infrastructure). The code that runs under the Common Language Runtime is termed as the Managed Code. In other words, you can say that CLR provides a managed execution enviornment for the .NET programs by
- 7. Continue…. The Common Language Runtime (CLR), the virtual machine component of Microsoft's .NET framework, manages the execution of .NET programs. Just-in-time compilation converts the managed code (compiled intermediate language code), into machine instructions which are then executed on the CPU of the computer. The CLR provides additional services including memory management, type safety, exception handling, garbage collection, security and thread management. All programs written for the .NET framework, regardless of programming language, are executed by the CLR. All versions of the .NET framework include CLR
- 8. Continue…. Below diagram illustrate that how CLR is associated with the operating system/hardware along with the class libraries. Here, runtime is actually CLR.
- 9. Role of CLR in the execution of a C# program… Suppose you have written a C# program and save it in a file which is known as the Source Code. Language specific compiler compiles the source code into the MSIL(Microsoft Intermediate Language) which is also know as the CIL(Common Intermediate Language) or IL(Intermediate Language) along with its metadata. Metadata includes the all the types, actual implementation of each function of the program. MSIL is machine independent code. Now CLR comes into existence. CLR provides the services and runtime environment to the MSIL code. Internally CLR includes the JIT(Just-In-Time) compiler which converts the MSIL code to machine code which further executed by CPU. CLR also uses the .NET Framework class libraries. Metadata provides the information about the programming language, environment, version, and class libraries to the CLR by which CLR handles the MSIL code. As CLR is common so it allows an instance of a class that written in a different languague to call a method of the class which written in another langauge.
- 10. Continue….
- 11. Continue CLR As the word specify Common which means CLR provides a common runtime or execution environment as there are more than 60 .NET programming languages. Main componenets of CLR: Common Language Specification (CLS) Common Type System (CTS) Garbage Collection (GC) Just In – Time Compiler (JIT)
- 12. Common Language Specification (CLS): It is responsible for converting the different .NET programming language syntactical rules and regulations into CLR understandable format. Basically, it provides the Language Interoperability. Language Interoperability means to provide the execution support to other programming languages also in .NET framework. Language Interoperability can be achieved in two ways : Managed Code and Unmanaged Code. Managed Code: The MSIL code which is managed by the CLR is known as the Managed Code. For managed code CLR provides three .NET facilities: CAS(Code Access Security) Exception Handling Automatic Memory Management. Unmanaged Code: Before .NET development the programming language like .COM Components & Win32 API do not generate the MSIL code. So these are not managed by CLR rather managed by Operating System which is called unmanaged code.
- 13. Common Type System (CTS) Every programming language has its own data type system, so CTS is responsible for the understanding all the data type system of .NET programming languages and converting them into CLR understandable format which will be a common format. There are 2 Types of CTS that every .NET programming language have : Value Types: Value Types will directly store the value directly into the memory location. These types work with stack mechanism only. CLR allots memory for these at Compile Time. Reference Types: Reference Types will contain a memory address of value because the reference types won’t store the variable value directly in memory. These types work with Heap mechanism. CLR allots memory for these at Runtime
- 14. Garbage Collector It is used to provide the Automatic Memory Management feature. Suppose if there is no garbage collector then programmers have to write the memory management codes which will be a kind of overhead on programmers.
- 15. JIT(Just In Time Compiler) It is responsible for converting the CIL(Common Intermediate Language ) into machine code or native code using the Common Language Runtime environment.
- 16. Benefits of CLR It improves the performance by providing a richly interact between programs at the run time. Enhance portability by removing the need of recompiling a program on any operating system that support it. Security also increases as it analyze the MSIl instructions whether they are safe or unsafe. Also, the use of delegates in place of function pointers enhance the type safety and security. Support automatic memory managment with the help of Garbage Collector. Provides cross language integration because CTS inside CLR provides a common standard that activate the different languages to extend and share each other’s libraries. Provides support to use the components that developed in other .NET programming languages. Provide language, platform, and architecture independency. It allows the creation of the scalable and multithreaded applications in a easier way as developer has no need to think about the memory management and security isssues.
- 17. Microsoft Intermediate Language (MSIL) .NET programming language (C#, VB.NET, J# etc.) does not compile into executable code; instead it compiles into an intermediate code called Microsoft Intermediate Language (MSIL). As a programmer one need not worry about the syntax of MSIL - since our source code in automatically converted to MSIL. The MSIL code is then send to the CLR (Common Language Runtime) that converts the code to machine language which is then run on the host machine. Common Intermediate Language (CIL), formerly called Microsoft Intermediate Language (MSIL), is the lowest-level human-readable programming language defined by the Common Language Infrastructure (CLI) specification and is used by the .NET Framework, .NET Core, and Mono. Languages which target a CLI-compatible runtime environment compile to CIL, which is assembled into an object code that has a bytecode-style format. CIL is an object-oriented assembly language, and is entirely stack-based. Its bytecode is translated into native code or—most commonly—executed by a virtual machine. The execution process looks like this: Source code is converted to CIL i.e. Common Intermediate Language, which is the CLI's equivalent to assembly language for a CPU. CIL is then assembled into a form of so-called bytecode and a CLI assembly is created. Upon execution of a CIL assembly, its code is passed through the runtime's JIT compiler to generate native code. Ahead-of-time compilation may also be used, which eliminates this step, but at the cost of executable-file portability. The computer's processor executes the native code. MSIL is similar to Java Byte code. A Java program is compiled into Java Byte code (the .class file) by a Java compiler, the class file is then sent to JVM which converts it into the host machine language.
- 18. Irshad Ahmad Dar 148 | Chukar | Kunzar | Baramulla, | J&K +91 7006 758 559 || +91 9596 296 [email protected] A Ray Of Hope PK DO YOU HAVE ANY Q UERRY ?