Basics of .NET Framework

1. UNIT 1
Chapter 2
.NET FRAMEWORK

2. .Net Framework
• .Net Framework is the heart of the microsoft
.NET
• .Net Framework provides the necessary
compile time and run time foundation to build
and run .NET based applications

3. Common language infrastructure
• Common Language Infrastructure (CLI)
enables an application program written in any
commonly-used programming languages to be
run on any operating system using a common
runtime program rather than a specific for
every language.

4. Common language infrastructure

5. CLI basic elements
1. Common Language Infrastructure (CLI)
2. Common Type System (CTS)
3. Common Language Specification (CLS)
4.Virtual Execution System (VES)

6. CLI basic elements
• The Common Type System (CTS): A set of data
types and operations that are shared by all CTS-
compliant programming languages.
• The Common Language Specification (CLS):The CLI
should conform with the set of base rules to which any
language targeting, since that language should
interoperate with other CLS-compliant languages. The
CLS rules define a subset of the Common Type System.
• The Virtual Execution System (VES)The VES loads and
executes CLI-compatible programs, using the metadata
to combine separately generated pieces of code at
runtime.

7. Relation

8. Common Type System(CTS)
• The common type system defines how types are declared, used,
and managed in the common language runtime, and is also an
important part of the runtime's support for cross-language
integration. The common type system performs the following
functions:
• Establishes a framework that helps enable cross-language
integration, type safety, and high-performance code execution.
• Provides an object-oriented model that supports the complete
implementation of many programming languages.
• Defines rules that languages must follow, which helps ensure that
objects written in different languages can interact with each other.
• Provides a library that contains the primitive data types (such
as Boolean, Byte, Char, Int32, and UInt64) used in application
development.

9. Common Language Specification(CLS)
CLS is set of rules to design any language to support .NET framework

10. MSIL(Microsoft Intermediate
Language)
• .NET programming language does not compile
into executable code instead it compiles into
an intermediate code
• MSIL code is then send to CLR that converts
the code to machine langaugae it run on host
machine.
• MSIL is similar to java byte code

11. Just in time (JIT) Compiler
• CPU Specific code that runs on the same
computer architecture as the JIT compiler.
• The CLR supplies a JIT compiler for each
supported CPU architecture, developers can
write a set of MSIL that can be JIT compiled
and run on computers with different
architectures.

12. Managed and Unmanaged code
• It is a code that written to target the services
of the common language runtime.
• All C#, Visual Basic .NET, and Jscript .NET code
is managed by default
• Visual Studio .NET C++ code is not managed
by default, but the compiler can produce
managed code.

13. Net Framework Architecture
• .Net Framework Architecture is a
programming model for the .Net platform that
provides an execution environment and
integration with various programming
languages for simple development and
deployment of various Windows and desktop
applications. It consists of class libraries and
reusable components.

14. .Net Framework Architecture

15. .NET Components
1. Common Language Runtime
The CLI has the following key features:
• Exception Handling
• Garbage Collection
• Working with Various programming languages

16. Exception Handling
• Exceptions are errors which occur when the
application is executed.Examples of
exceptions are:
• If an application tries to open a file on the
local machine, but the file is not present.
• If the application tries to fetch some records
from a database, but the connection to the
database is not valid.

17. Garbage Collection
• Garbage collection is the process of removing
unwanted resources when they are no longer
required.Examples of garbage collection are
• A File handle which is no longer required. If the
application has finished all operations on a file,
then the file handle may no longer be required.
• The database connection is no longer required. If
the application has finished all operations on a
database, then the database connection may no
longer be required.

18. Class Library
• A class library is a collection of methods and
functions that can be used for the core
purpose.
• For example, there is a class library with
methods to handle all file-level operations. So
there is a method which can be used to read
the text from a file. Similarly, there is a
method to write text to a file.

19. Languages
• WinForms
• ASP.Net
• ADO.Net