What's New in the .NET Framework Version 2.

The Microsoft .NET Framework version 2.0

extends the .NET Framework version 1.1
with new features, improvements to
existing features, and enhancements to the
documentation. This section provides
information about some key additions and
modifications.
 64-Bit Platform Support

The new generation of 64-bit computers

enables the creation of applications that
can run faster and take advantage of
more memory than is available to 32-bit
applications. New support for 64-bit
applications enables users to build
managed code libraries or easily use
unmanaged code libraries on 64-bit
 Access Control List Support
An access control list (ACL) is used to grant or
revoke permission to access a resource on a
computer. New classes have been added to the
.NET Framework that allow managed code to
create and modify an ACL. New members that use
an ACL have been added to the I/O, registry, and
threading classes
 Manifest-Based Activation

This feature provides new support for loading and

activating applications through the use of a manifest.
Manifest-based activation is essential for supporting Click
Once applications. Traditionally, applications are activated
through a reference to an assembly that contains the
application's entry point. For example, clicking an
application's .exe file from within the Windows shell causes
the shell to load the common language runtime (CLR) and
call a well-known entry point within that .exe file's
assembly.
The manifest-based activation model uses an
application manifest for activation rather than an
assembly. A manifest fully describes the application, its
dependencies, security requirements, and so forth. The
manifest model has several advantages over the
assembly-based activation model, especially for Web
applications. For example, the manifest contains the
security requirements of the application, which enables
the user to decide whether to allow the application to
execute before downloading the code. The manifest
also contains information about the application
dependencies.
Manifest-based activation is provided by a set of APIs
that allow managed hosts to activate applications and
add-ins described by a manifest. These APIs contain a
mixture of both new classes and extensions to existing
classes.

This activation model also invokes an entity called

a Trust Manager that performs the following tasks:
1.Determines whether an application is allowed to be activated. This
decision can be made by prompting the user, querying policy, or by any
other means deemed appropriate for a given Trust Manager.
2.Sets up the security context to run an application in. Most commonly,
this step involves setting up a code access security (CAS) policy tree on
the application domain in which the application will run.
 The Quickie Bullet List
(1/5)
v 64-bit Platform Support
v Access Control List Support *
v ADO.NET Enhancements *
v ASP.NET Enhancements **
v Authenticated Streams
v COM Interoperability
Enhancements
v Console Class Additions
v Data Protection API *
 The Quickie Bullet List (2/5)

v Debugger Edit and Continue

Support *
v Detect Network Connectivity
Events
v Distributed Computing
Enhancement
v Event Log Support Enhancements
v Expanded Certificate Management
v FTP Client Support *
v Generics / Generic Collections *
 The Quickie Bullet List
(3/5)

v Manifest-Based Activation
v .NET Framework Remoting
Enhancements
v Obtain Local Network Information
*
v Ping Support *
v Processing HTTP Requests from
Within
vApplications
v Programmatic Control of Caching
 The Quickie Bullet List
(4/5)
v Serial I/O Device Support
v Serialization Enhancements
v SMTP Support Enhancements
v Strongly Typed Resource Support
v Threading Improvements
v Trace Data Filtering
v Transactions
v Web Services Updates
v Windows Forms Updates *
 The Quickie Bullet List
(5/5)
What’s New in the
.NET
Framework 2.0
Created By:- Ashirvadi
Nath Dwivedi
Sub Topic:- Manifest-
Based Activation