Basic of Microsoft .Net Framework, Covering following topics: .Net Framework Why .Net? Framework Architecture Code execution process IL, CLR, CLS, CTS JIT compiler Manage-Unmanaged Code Garbage Collection

1. Microsoft .NET
(Introduction to .Net Framework)
Rohit Rao

2. Agenda
• .Net Framework
• Why .Net?
• Framework Architecture
• Code execution process
• IL, CLR, CLS, CTS
• JIT compiler
• Manage-Unmanaged Code
• Garbage Collection

3. .Net Framework
• Building blocks of any .Net application
– Windows form
– Web Application
– Web Service
– Console application
• Collection of assemblies to support
development & execution of .Net apps.
• Network of all technologies / Next Gen Tech

4. Why .Net?
• Automatic Memory Management
• Interoperable
• Choice of programming Languages
– C#, VB, VC++, Python etc.
– Producing same compiled code
• Language integration is seamless
– Easily call or integrate multiple languages code

5. .Net Framework Architecture
Visual Studio
Asp.Net
(Web/MVC/SPA)
Windows Form
(Desktop App)
ADO.NET
ADO.NET
EF
LINQ Signal R
WPF Web Services SilverLight Windows Store App
Base Class Lib.
ADO.NET
EF
Languages (C#,
Vb, Python etc.)
Dynamic Language
Runtime
MEF
Portable Class
Library
CLR
(Common Language Runtime)

6. Code Execution Process
C#
Code
VB.Net
Code
Other
CSC.exe VBC.exe Respective
Compiler
IL Code /
MSIL metadata
Execution Engine
Common Language Runtime (CLR)
Just In Time (Reads IL Code)
Machine Specific Instructions

7. IL (Intermediate Language)
• Partially / Half Compiled Code
• CPU Independent Code
• Why we need it?
– We do not know the environment on which
application will run
• Machine Configuration (Windows 7 /8 / 10 / etc.)
• Security Configuration
• Use ILDASM tool to view IL code

8. CLR (Common Language Runtime)
• Heart of .NET Framework
• It does following things :
– Garbage Collection
– CAS ( Code Access Security)
– CV (Code Verification)
– IL to native translation (Code)

9. CTS (Common Type System)
• Smooth Communication between .NET
languages (C#, VB.Net, VC++ etc)
• It ensures that data types of languages will get
compiled to a common Data Type.
C#
int
VB.Net
integer
System.Int32

10. CLS (Common Language Specification)
• Subset of CTS
• Set of rules which need to be followed by each
.NET language

11. Just in Time Compiler (JIT)
• It Converts IL code to native / machine specific
instructions
• IT compiles code in following way
– Per File (Whole file)
– Per Method (only modified / changed methods )
– Code Fragment (only modified code)
• Types of JIT
– Normal JIT : Dynamic Compilation with cache
– Econo JIT : Dynamic Compilation without cache
– Pre-JIT : Full Compilation using Ngen.exe (Manually)

12. Manage-Unmanaged Code
• Managed Code :
– Exe / Web App in created in .Net
• These runs under the control of CLR
• CLR use GC to clean unused objects
• CLS for interoperability
• CAS , CV
• Un-Managed :
– Third party libraries : Excel / Skype / GotoMeeting
– CLR does not have control
– Their respective runtime will be used to control
them (C/C++/VB6 etc)

13. Garbage Collection
• Why we need it?
– Clean unused managed objects to reclaim
memory
• GC Generation:
– 0
– 1
– 2

14. Gen 0 Gen 1 Gen 2
Gen 0 Gen 1 Gen 2
Gen 0 Gen 1 Gen 2
Gen 0 Gen 1 Gen 2
GC contd..
App 1 creates 7 objects
GC Runs & Claims Memory
GC Runs & Claims Memory
GC Runs & Claims Memory

15. Data Types
C# Data Types
Value Types Reference Types
Simple Enum Struct Nullable
Class String Object
Sbyte,
byte,
Decimal
Short,
Ushort,
Int,
Uint,
Long,
ULong
Char
Float,
Double,
Decimal
Bool
Class
Types
Interface Arrays Delegate
Integral
Character
s
Floating /
Decimal
Boolean