CVM UNIVERSITY

INSTITUTE OF SCIENCE & TECHNOLOGY FOR ADVANCED STUDIES &

RESERCH(ISTAR)
Constituent College of CVM University
1stRank among all Colleges of Gujarat by KCG (GSIRF) – 2021
Recognized under Section 2(f) and 12(B) of the UGC Act, 1956

ACADEMIC YEAR 2021-22

M.SC. (INFORMATION TECHNOLOGY) SEMESTER - I
PAPER CODE (Title): 101410113 (ASP.NET Using C#)
FACULTY NAME: DR. SUCHITA PATEL

Unit 1: Introduction to .NET Framework - Architecture of .NET Framework – BCL (Base

Class Library), CLR (Common Language Runtime), Etc. - .NET Languages – Introduction,
Types of Applications Supported by .NET Technology - Managed Code, Compilation to
Intermediate Language, Just-In-Time Compilation, Garbage Collection, Assemblies and
the GAC

Unit 2: C#.NET – Introduction and Features - General Structure of C#.NET Program -

C#.NET – Basic Data Types, Variable, Constant, Type Conversion - Boxing and Unboxing
- C#.NET – Statements (Conditional and Looping) – Types of Applications. Advance
Features - OOPS Concepts, Class and Object - Inheritance; Polymorphism – Overloading,
Overriding, Etc., Class Types and Interface - Working with Strings, Arrays, Lists and
Collections - Exception Handling

Unit 3: Introduction To ASP.NET And Programming In ASP.NET; Web Server – Internet

Information Server (IIS); Architecture Of ASP.NET; ASP.NET Page Lifecycle; ASP .NET
Page Directives; Controls – HTML Controls And ASP.Net Server Controls ; Control
Properties And Events ; PostBack ; Exception Handling ; Validation Controls ; Navigation
Controls ; Login Controls; MasterPages Web Application Management; State
Management; ViewState; Application; Session; Cookie; QueryString; Web.Config And
Machine.Config ; Global.Asax ; Authentication Methods ; Caching

Unit 4: Database Programming with ADO.NET and Reports - The ADO.NET architecture
(connected and disconnected mode) - ADO.NET Data providers, Dataset, DataAdapter,
DataReader - Working with Data Controls; Design time data binding; Runtime data
binding; Working with Stored Procedures, Generating reports

Reference Books:
1. C# and the .NET Platform by Andrew Troelsen : APress
2. C# The Basics by Vijay Mukhi : BPB
3. C# Essentials by Ben Albabari : O’Reilly
4. Professional C# by Simon Robinson : Wrox
5. ASP.NET - A Beginner’s guide by Dave Mercer : TMH
6. Professional ASP.NET : Wrox.
7. ASP.NET Programmer’s Reference : Wrox
8. ADO.NET Programmer’s Reference : Wrox.
9. Professional C# 2008 by Christian Nagel : Wrox
10. C# The Nuts & Bolts by Akash Sarat & Sonal Mukhi : BPB
11. C# Made Simple : BPB Publication
12. C# 3.0 Unleashed: With the .NET Framework 3.5 by Joseph Mayo : Sams
 Unit 1
Introduction to .NET Framework - Architecture of .NET Framework – BCL (Base Class
Library), CLR (Common Language Runtime), Etc. - .NET Languages – Introduction,
Types of Applications Supported by .NET Technology - Managed Code, Compilation to
Intermediate Language, Just-In-Time Compilation, Garbage Collection, Assemblies and
the GAC

 Introduction to .NET Framework:

What is .Net Framework?

.Net Framework is a software development platform developed by Microsoft for
building and running Windows applications.

The .Net framework consists of developer tools, programming languages, and libraries
to build desktop and web applications.

It is also used to build websites, web services, and games.

.NET is a framework tool that supports many programming languages and many
technologies, .NET support 60+ programming languages.

In 60+ programming languages, 9 are designed by Microsoft and the remaining are
designed by non-Microsoft.

Microsoft designed programming languages are as follows

1. VB.NET
2. C#.NET
3. VC++.NET
4. J#.NET
5. F#.NET
6. Jscript.NET
7. Windows PowerShell
8. Iron python
9. Iron Ruby

Technologies supported by the .NET framework are as follows

1. ASP.NET (Active Server Pages.NET)
2. ADO.NET (Active Data Object.NET)
3. WCF (Windows Communication Foundation)
4. WPF (Windows Presentation Foundation)
5. WWF (Windows Workflow Foundation)
6. AJAX (Asynchronous JavaScript and XML)
7. LINQ (Language Integrated Query)
  .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 types of applications.
It is a framework developed by Microsoft and it basically runs on Microsoft windows. Its
first beta version was 1.0 which was released in the year 2002.
It is a framework for developing a console base, window-based application, and web-
based application.
This framework supports many programming languages like C# and Visual Basics.
So it’s easy for the developer to choose any language to develop their required
application.
It consists of class libraries and reusable components.
Components of .NET Framework Architecture
The architecture of the .net framework is based on .net component.
Let’s have a look at its component and its description of its architecture with the help of
its diagram.
.Net Framework is a platform that provides tools and technologies to develop Windows,
Web and Enterprise applications. It mainly contains two components,
1. Common Language Runtime (CLR)
2. .Net Framework Class Library.

1. CLR (Common Language Runtime)

.Net Framework provides runtime environment called Common Language
Runtime (CLR).It provides an environment to run all the .Net Programs.
The code which runs under the CLR is called as Managed Code. Programmers need not
to worry on managing the memory if the programs are running under the CLR as it
provides memory management and thread management.

Programmatically, when our program needs memory, CLR allocates the memory for
scope and de-allocates the memory if the scope is completed.

Language Compilers (e.g. C#, VB.Net, J#) will convert the Code/Program to Microsoft
Intermediate Language (MSIL) intern this will be converted to Native Code by CLR. See
the below Fig.

There are currently over 15 language compilers being built by Microsoft and other
companies also producing the code that will execute under CLR.

There are two types of code categorized in .net framework:

One manages code that will run and execute under the CLR environment.
Another one is unmanaged code which will not run and execute in the CLR
environment. Also, it supports multiple languages that simplify application
development.
It has many major features so Let’s have a look at its major features.

 Code Access security

 Memory management
 Thread support
 Debug engine
 Capabilities in optimizing, securing and providing robust capabilities like
application deployment and side by side execution.
 Garbage collection which removes unwanted resources when it is not required
 Exception handling which includes cross-language exceptions. Exceptions are
errors when the program or application is executed
 JIT Compilation (Just-In-Time)

Suppose we wrote a program and it needs memory, CLR now allocates the memory for
the program in scope and de-allocates the memory when it is not required or it is
completed.

2. .Net Framework Class Library (FCL)

This is also called as Base Class Library and it is common for all types of applications i.e.
the way you access the Library Classes and Methods in VB.NET will be the same in C#,
and it is common for all other languages in .NET.

The following are different types of applications that can make use of .net class library.

 Windows Application.
 Console Application
 Web Application.
 XML Web Services.
 Windows Services.

In short, developers just need to import the BCL in their language code and use its
predefined methods and properties to implement common and complex functions like
reading and writing to file, graphic rendering, database interaction, and XML document
manipulation.

Below are the few more concepts that we need to know and understand as part of this
.Net framework.

3. Common Type System (CTS)

It describes set of data types that can be used in different .Net languages in common.
(i.e), CTS ensures that objects written in different .Net languages can interact with each
other.
For Communicating between programs written in any .NET complaint language, the
types have to be compatible on the basic level.

The common type system supports two general categories of types:

Value Types:

Value types directly contain their data, and instances of value types are either allocated
on the stack or allocated inline in a structure. Value types can be built-in (implemented
by the runtime), user-defined, or enumerations.

Reference types:

Reference types store a reference to the value's memory address, and are allocated on
the heap.
Reference types can be self-describing types, pointer types, or interface types.
The type of a reference type can be determined from values of self-describing types.
Self-describing types are further split into arrays and class types.
The class types are user-defined classes, boxed value types, and delegates.

4. Common Language Specification (CLS)

It is a sub set of CTS and it specifies a set of rules that needs to be adhered or satisfied
by all language compilers targeting CLR.
It helps in cross language inheritance and cross language debugging.

Common language specification Rules:

It describes the minimal and complete set of features to produce code that can be
hosted by CLR.
It ensures that products of compilers will work properly in .NET environment.

Sample Rules:
1. Representation of text strings
2. Internal representation of enumerations
3. Definition of static members and this is a subset of the CTS which all
.NET languages are expected to support.
4. Microsoft has defined CLS which are nothing but guidelines that
language to follow so that it can communicate with other .NET
languages in a seamless manner.
  Benefits of .Net Framework:

Consistent Programming Model:

.Net Framework provides a consistent object-oriented programming model across
different languages.

Using this model you can do different task such as connecting to and retrieving data
from databases, and reading from and writing to files.

Cross – Platform Support:

.Net application enables interoperability between multiple windows operating system.
Language Interoperability:
This feature enables codes written in different languages to interact with each other.
This helps in reuse of code and improves the efficiency of the development process.
For example, if you create a class in visual basic and a class in C#, you can inherit the C#
class in Visual Basic and vise versa.

Automatic Management of Resource:

When you create an application by using .Net, you do not need to manually free the
application resources, such as files, memory and network and database connections.

.Net framework provides feature called CLR, which automatically tracks the resource
usage and relieves users from the task of manual resource management.

Ease of deployment:
In most cases, to install an application, you need to copy the application, along with its
component, on the target computer.

.Net framework provides easy deployment of applications in the form of assemblies.

An assembly is compiled code library used for deployment, versioning and security.

There are two types: Proccess assemblies (.exe) and Library assemblies (.dll)

 Code Execution Process

The Code Execution Process involves the following two stages:

1. Compiler time process.

2. Runtime process.
1. Compiler time process

1. The .Net framework has one or more language compilers, such as Visual Basic,
C#, Visual C++, JScript, or one of many third-party compilers such as an Eiffel,
Perl, or COBOL compiler.
2. Anyone of the compilers translates your source code into Microsoft Intermediate
Language (MSIL) code.
3. For example, if you are using the C# programming language to develop an
application, when you compile the application, the C# language compiler will
convert your source code into Microsoft Intermediate Language (MSIL) code.
4. In short, VB.NET, C#, and other language compilers generate MSIL code. (In other
words, compiling translates your source code into MSIL and generates the
required metadata.)
5. Currently "Microsoft Intermediate Language" (MSIL) code is also known as the
"Intermediate Language" (IL) Code or "Common Intermediate Language" (CIL)
Code.

SOURCE CODE -----.NET COMLIPER------> BYTE CODE (MSIL + META DATA)

2. Runtime process.
1. The Common Language Runtime (CLR) includes a JIT compiler for converting
MSIL to native code.
2. The JIT Compiler in CLR converts the MSIL code into native machine code that is
then executed by the OS.
3. During the runtime of a program, the "Just in Time" (JIT) compiler of the
Common Language Runtime (CLR) uses the Metadata and converts Microsoft
Intermediate Language (MSIL) into native code.

BYTE CODE (MSIL + META DATA) ----- Just-In-Time (JIT) compiler------>

NATIVE CODE
  Garbage Collector in .NET Framework

The Garbage collection is very important technique in the .Net framework to free the
unused managed code objects in the memory and free the space to the process.

Garbage Collection in .Net framework

The garbage collection (GC) is new feature in Microsoft .net framework. When we have a
class that represents an object in the runtime that allocates a memory space in the heap
memory. All the behavior of that objects can be done in the allotted memory in the heap.
Once the activities related to that object is get finished then it will be there as unused
space in the memory.

The earlier releases of Microsoft products have used a method like once the process of
that object get finished then it will be cleared from the memory. For instance Visual
Basic, An object get finishes that work then there we have to define a "nothing" to that
object. So, it clears the memory space to the processors.

Microsoft was planning to introduce a method that should automate the cleaning of
unused memory space in the heap after the life time of that object. Eventually they have
introduced a new technique "Garbage collection". It is very important part in the .Net
framework. Now it handles this object clear in the memory implicitly. It overcomes the
existing explicit unused memory space clearance.

How Garbage Collection Works

Implicit Garbage Collection should be handled by the .Net framework. When object is
created then it will be placed in the Generation 0. The garbage collection uses an
algorithm which checks the objects in the generation, the objects life time get over then
it will be removed from the memory. The two kinds of objects. One is Live Objects and
Dead Objects. The Garbage collection algorithm collects all unused objects that are dead
objects in the generation. If the live objects running for long time then based on that life
time it will be moved to next generation.

The object cleaning in the generation will not take place exactly after the life time over
of the particular objects. It takes own time to implement the sweeping algorithm to free
the spaces to the process.

Exception Handling

The Garbage collection has designed such a way that it can be implicitly handling to
collect the free spaces in memory. But as I said it takes own time to uses the algorithm
to collect unused objects in the memory.

If we want to forces to collect unused objects or explicitly release particular object from
the memory. The code allows us to clear the object from the heap immediately.