.Net Session Overview
1 like•507 views
The .NET Framework provides a consistent programming environment, supports multiple languages and platforms, and simplifies component interaction. It includes the Common Language Runtime (CLR) and .NET Framework Class Library. The CLR handles memory management, security, and execution of code and compiles source code into Microsoft Intermediate Language (MSIL) and metadata. Assemblies are the fundamental unit of deployment and versioning. The .NET Framework Class Library includes types for common tasks like I/O, data access, and the user interface.
.Net Session Overview
- 1. Overview .Net Frame Work Overview ASP .Net Demonstration Deploying Asp .Net Web App
- 2. .Net Framework Design Consideration To provide a consistent object-oriented programming environment To provide a code-execution environment that minimizes software deployment and versioning conflicts To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
- 3. .Net Framework Components Common Language Runtime(CLR) .Net Framework Class Library
- 4. .NET Framework in context
- 5. Two Step Compilation Language (c# or VB .Net) code to Microsoft Intermediate Language (MSIL) –VS 2008. MSIL to byte code - CLR
- 6. CLR –What is provides ? cross-language integration. cross-language exception handling. enhanced security. versioning and deployment support. simplified model for component interaction and debugging and profiling services.
- 7. Closer Look into CLR Managed Execution Process Choosing a compiler Compile ur code to MSIL MSIL to native code Running code
- 8. Choosing Compiler VS 2008 3 rd party compilers such as an Eiffel, Perl, or COBOL compiler. Common Language Specification
- 9. Compiling to MSIL MSIL - It includes instructions for loading, storing, initializing, and calling methods on objects, as well as instructions for arithmetic and logical operations, control flow, direct memory access, exception handling etc. Metadata - It describes the types in your code, including the definition of each type, the signatures of each type's members, the members that your code references, and other data that the runtime uses at execution time. The MSIL and metadata are contained in a portable executable (PE) file that is based on and extends the published Microsoft PE and common object file format (COFF) used historically for executable content
- 10. Compiling MSIL to Native code- CLR Just In Time (JIT) compilation Compilation happening at runtime as needed. Improves load time performance. Code verification: A reference to a type is strictly compatible with the type being referenced. Only appropriately defined operations are invoked on an object. Identities are what they claim to be .
- 11. Automatic Memory Management Allocating Memory: Managed heap (ref type). Releasing Memory: Active roots Unreachable objects are removed based effective algorithm Releasing Memory for Unmanaged Resources: Dispose()
- 12. Common Type System Type classification: Value types Reference types.
- 13. Metadata and Self-Describing Components Metadata describes every type and member defined in your code in a language-neutral manner. Metadata stores the following information: Description of the assembly. Identity (name, version, culture, public key). The types that are exported. Other assemblies that this assembly depends on. Security permissions needed to run. Description of types. Name, visibility, base class, and interfaces implemented. Members (methods, fields, properties, events, nested types). Attributes. Additional descriptive elements that modify types and members.
- 14. Assemblies Assemblies are a fundamental part of programming with the .NET Framework. security boundary version boundary deployment boundary Side by side execution (multiple versions of a component to be run simultaneously). Solves versioning issues An End to DLL conflicts Provide infrastructure for versioning rule
- 15. Assembly Contents Single File Assembly: Multi file Assembly:
- 16. Application Domain Provides Isolation between application in a single process. App domains Process
- 17. App Domain benefits Faults in one application cannot affect other applications Code running in one application cannot directly access code or resources from another application. The common language runtime enforces this isolation by preventing direct calls between objects in different application domains Improves performance by reducing cross-process calls or switching between processes
- 18. .NET Framework Class Library Overview Represent base data types and exceptions. Encapsulate data structures. Perform I/O. Access information about loaded types. Invoke .NET Framework security checks. Provide data access, rich client-side GUI, and server-controlled, client-side GUI. Object (System. Object) Collections Generics Reflection
- 19. Runtime Hosts The runtime host loads the runtime into a process, creates the application domains within the process, and loads user code into the application domains. Ex: Asp .Net - Loads the runtime into the process that is to handle the Web request. ASP.NET also creates an application domain for each Web application that will run on a Web server.
- 20. Questions ? Questions ?
- 21. Thank You Logu T