Scribd
Upload
78 views

Dot Net Platform Fundamentals

The document discusses .NET Framework and compares ASP vs ASP.NET. It provides details on Common Language Runtime (CLR) features like memory management, security, code verification, and interoperability. It includes an example "Hello World" C# program and discusses assemblies, intermediate language, manifests, and deploying assemblies to the Global Assembly Cache.

Uploaded by

Roshan212
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
78 views

Dot Net Platform Fundamentals

The document discusses .NET Framework and compares ASP vs ASP.NET. It provides details on Common Language Runtime (CLR) features like memory management, security, code verification, and interoperability. It includes an example "Hello World" C# program and discusses assemblies, intermediate language, manifests, and deploying assemblies to the Global Assembly Cache.

Uploaded by

Roshan212
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

DOT NET FRAMEWORK is a programming infrastructure or platform prepared by

Microsoft for building, deploying, and executing applications. Application can be


console, windows, web etc.
CLASSICAL ASP vs ASP.NET

ASP (Active Server Pages) is a combination of HTML code and jscript or


vbscript whereas ASP.NET is based on code behind model and supports about
42 languages.

ASP engine executes server side coding and script is interpreted but ASP.NET
is based on dual compilation.

ASP.NET code is easy to debug at compile time and is very easy to deploy.

ASP.NET is completely based on OOP and provides thousands of interfaces,


classes and methods for easy programming.

programming tasks such as string management, data collection and file


access.

Some More on CLR: Common Language Infrastructure (CLI) contains


specification for the runtime environment.

Common Language Runtime (CLR) is an implementation of CLI and is the


runtime environment for .NET applications. CLR is the Virtual Execution
Environment.

The portion of the CLR that performs the tasks of loading, running, and
managing .NET applications is called the virtual execution system (VES).

Common Type system (CTS) defines how the primitive data types and
complex data types are declared and used at runtime.

Common Language Specification (CLS) all instructions of CTS are written


here.

Code Manager (CM) Invokes class loader for execution.

Garbage Collector (GC) Performs automated garbage collection.

The Class Library is an object oriented collection of reusable types that


integrate with the CLR.

It is object oriented and provides types from which user defined types can derive
functionality. This makes for ease of use and is time saving.Third party components
can be integrated seamlessly with classes in the .NET framework. It enables a range
of common
CLR Features
1. CLR manages memory, thread execution, code execution, compilation code
safety verification and other system services.
2. For security reasons, managed code is assigned varying degrees of trust
based on origin. This prevents or allows the managed component from
performing file access operations, registry access operations or other
sensitive functions even within the same active application.
3. The Runtime enforces code robustness by implementing strict type and
code verification infrastructure called Common type System (CTS). The CTS
ensures that all managed code is self describing and all Microsoft or third
party language compiler generated codes conform to CTS. This enables the
managed code to consume other managed types and enforce strict type
fidelity and type safety.

4. CLR eliminates many common software issues like handling of object


layout, references to objects and garbage clearance. This type of memory
management prevents memory leaks and invalid memory references.
5. The CLR also accelerates developer productivity. The programmers are free
to choose the language of the application without worrying about
compatibility and integration issues. He is also enabled to take advantage of
the runtime and the class library of the .NET Framework and also harvest
components from other applications written in different languages by
different developers. This implicitly eases the process of migration.
6. Though CLR facilitates interoperability between the managed and
unmanaged.
7. The design of the CLR is geared towards enhancing performance. The Justin-time (JIT) compiling enables managed code to run in the native machine
language of the system executing it. During the process the memory
manager removes the possibilities of fragmented memory and increases
memory locality-of-reference to enhance performance.
8. Finally, server side applications can host runtime. High performance
servers like Microsoft SQL Server and Internet Information Services can host
this CLR and the infrastructure so provided can be used to write business
logic while enjoying the best benefits of enterprise server support.

My First Program:
/*
HelloWorld.cs - First C# Program
By - Roshan
*/
public class HelloWorld
{
public static void Main()
{
//Print Hello World
System.Console.WriteLine("Hello World !");
System.Console.Read();
}
}
Try compiling via Visual Studio and also via VS command prompt

ASSEMBLY

After compilation MSIL code is stored in portable, versionable, reusable and


self-describing assemblies. Assembly can be single File Assembly and Multiple
Assembly.

Assembly can be a .dll or .exe file based on the main() method.

Anatomy of Assembly:

Intermediate language (IL or MSIL)


This is a processor independent representation of executable code. It is similar to
assembly code and specific to the CLR. It is generated by the language compilers
that target the CLR. At runtime, the CLR just-in-time compiles the IL to native code
for execution. The tool ngen.exe which is part of the .NET framework pre-compiles
assemblies to native code at install time and caches the precompiled code to the
disk.
Manifests, Metadata and Attributes
Metadata and manifests are key aspects of managed code execution. The portions
of an assembly that contains descriptive information about the types contained in
the assembly, the members exposed by the assembly and the resources required by
the assembly are called manifests. Metadata is contained within the manifest. This
metadata describes the assembly and some of it is generated by the language
compiler at compile time. Other metadata may be added by the developer at design
time. Declarations added to the code to describe or modify some aspect of the
codes behaviour at runtime are known as Attributes. These are stored with an
assembly as metadata. They serve many useful purposes in the .NET Framework
GAC: Global Assembly Cache C:\Windows\assembly
All the shared or public assemblies are kept in GAC. Steps to create a shared
assembly and deploy it in GAC
1. Open Visual Studio Command Prompt
2. Create a strong name key in CMD Prompt (SN -K
COMPLETE_FILENAME_OF_FILE_WHERE_KEY_HAS_TO_BE WRITTEN)
3. Add Strong Name file/key to assemblyinfo.cs file in the project
4. Build the project to get the shared/public assembly

5. Install the shared assembly in GAC via CMD Prompt (gacutil -i


DLLNAME_WITH_FULL_PATH)

You might also like