Dot Net Framework:- The .

NET Framework is Microsoft’s Platform for building

applications that have visually stunning user experiences, seamless and secure communication
and the ability to model a range of Business processes.

 The .NET Framework consists of:-

 Common language Runtime (CLR)- provide an abstraction layer over the operating
system.
 Base Class Library (BCL) - pre build code for common low-level programming task.
 Development frameworks & Technology- reusable & customizable solutions for larger
programming task.

Version’s of .net:-
A more complete listing of the releases of the .NET Framework may be found on the List of
.NET Framework versions.

 .NET Framework 1.0

This is the first release of the .NET Framework, released on 13 February 2002 and available
for Windows 98, Me, NT 4.0, 2000, and XP. Mainstream support by Microsoft for this version
ended 10 July 2007, and extended support ended 14 July 2009

 .NET Framework 1.1

This is the first major .NET Framework upgrade. It is available on its own as a redistributable

package or in a software development kit, and was published on 3 April 2003. It is also part

of the second release of Microsoft Visual Studio .NET. This is the first version of the .NET

Framework to be included as part of the Windows operating system, shipping with Windows

Server 2003.

 .NET Framework 2.0

1. The 2.0 Redistributable Package can be downloaded for free from Microsoft, and
was published on 22 January 2006.
2. The 2.0 Software Development Kit (SDK) can be downloaded for free from Microsoft
3. It is included as part of Visual Studio 2005 and Microsoft SQL Server 2005.
4. It shipped with Windows Server 2003
5. The 2.0 Redistributable Package can be downloaded for free from Microsoft, and
was published on 22 January 2006.
 6. The 2.0 Software Development Kit (SDK) can be downloaded for free from Microsoft.

 .NET Framework 3.0

.NET Framework 3.0, formerly called Win FX, was released on 21 November 2006. It includes a
new set of managed code APIs that are an integral part of Windows Vista and Windows Server
2008 operating systems. It is also available for Windows XP SP2 and Windows Server 2003 as
a download. There are no major architectural changes included with this release; .NET
Framework 3.0 uses the Common Language Runtime(CLR) of .NET Framework 2.0.Unlike the
previous major .NET releases there was no .NET Compact Framework release made as a
counterpart of this version. Version 3.0 of the .NET Framework shipped with Windows Vista. It
also shipped with Windows Server 2008 as an optional component (disabled by default).

.NET Framework 3.0 consists of four major new components:

 Windows Presentation Foundation (WPF), formerly code-named Avalon; a new user

interface subsystem and API based on XML and vector graphics, which uses 3D Computer
graphics hardware and Direct 3D technologies. See WPF SDK for developer articles and
documentation on WPF.
 Windows Communication Foundation (WCF), formerly code-named Indigo; a service-
oriented messaging system which allows programs to interoperate locally or remotely similar
to web services
 Windows Workflow Foundation (WWF) allows for building of task automation and
integrated transactions using workflow.
 Windows Card Space(WCP), formerly code-named Info Card; a software component
which securely stores a person's digital identities and provides a unified interface for
choosing the identity for a particular transaction, such as logging in to a website.

 .NET Framework 3.5

Version 3.5 of the .NET Framework was released on 19 November 2007, but it is not included
with Windows Server 2008. As with .NET Framework 3.0, version 3.5 uses the CLR of version
2.0. In addition, it installs .NET Framework 2.0 SP1, (installs .NET Framework 2.0 SP2 with 3.5
SP1) and .NET Framework 3.0 SP1 (installs .NET Framework 3.0 SP2 with 3.5 SP1), which
adds some methods and properties to the BCL classes in version 2.0 which are required for
version 3.5 features such as Language Integrated Query(LINQ). These changes do not affect
applications written for version 2.0, however.

COM(Component Object Model):-

A COM developers to access managed objects as easily as they access other COM objects.

The .NET Framework creates a type library and special registry entries when a component is
registered. It provides a specialized utility that exports the managed types into a type library
and registers the managed component as a traditional COM component. When the type is
instantiated through COM, the .NET CLR is the actual COM object that executes and it merely
marshals any method calls or property access to the type implementation.

 COM-------RCW-------.NET
The code of com is change in .NET By RCW(Runtime Callable Wrapper) is a tool
 .NET-------CCW-------Com
The code of .NET are change in COM code By CCW (Com Callable Wrapper) is also a
tool.

Advantages of .NET Framework:-

1. Applications running in a managed environment tend to require more system
resources than similar applications that access machine resources more directly.
2. Unobfuscated managed CIL byte code can often be easier to reverse-
engineer than native code. One concern is over possible loss of trade
secrets and the bypassing of license control mechanisms. Since Visual Studio
2002 Microsoft has included a tool to obfuscate code.
3. .NET Framework includes a garbage collector which runs periodically, on a
separate thread from the application's thread, that enumerates all the unusable
objects and reclaims the memory allocated to them.
4. Security isn't an issue as all the resources are available and accessed locally.
Consider an application that accesses data on a remote machine or has to
perform a privileged task on behalf of a non privileged user.
5. In .NET Web applications With classic ASP, when a developer needs to
present data from a database in a Web page, he is required to write
the application logic (code) and presentation logic (design) in the same file.
He was required to mix the ASP code with the HTML code to get the desired
result.
Dis-Advantages of .NET Framework:-

1. It'll only run on platforms that the .NET framework runs on. If you avoid P/Invoke
calls, then with the help of the Mono project this shouldn't be the problem.

2. You'll have to lower the semantic constructs in your language to a form represent

able in CIL instructions and the CLI object model. For procedural, strongly-typed,
optionally object oriented languages, this is rather simple. For functional or
dynamically typed languages, this can be quite a challenge, but you may get
some help from the DLR if you need those features.

3. In general, you won't have convenient access to machine intrinsic functions, so

for a language targeting high-performance/factorized scientific computing, you
may face some performance problems with the current implementations. Mono is
actively working on the issue, but neither Mono nor the .NET Framework has this
in place as "an established technology."