Differences between Dotnet2.0 and DotNet1.1:

1. Bulk Copy:

Copying of Data from one data source to
another data source in bulk like the sqlBulkCopy, this can
read as Dataset, Data Table and Data Reader. It provides
the fastest way to transfer the Data.

2. Batch Update:

Batch update can provide a huge
improvement in the performance by making just one round
trip to the server for multiple batch updates, instead of
several trips if the database server supports the batch
update feature. The UpdateBatchSize property provides the
number of rows to be updated in a batch. This value can be
set up to the limit of decimal.


3. Data Paging:

Now command object has a new execute
method called ExecutePageReader. This method takes three
parameters - Command Behavior, start Index, and page Size.
So if you want to get rows from 101 - 200, you can simply
call this method with start index as 101 and page size as
100.

4. Connection Details:
Now you can get more details about a
connection by setting Connection's Statistics Enabled
property to True. The Connection object provides two new
methods - Retrieve Statistics and Reset Statistics. The
Retrieve Statistics method returns a Hash Table object
filled with the information about the connection such as
data transferred, user details, curser details, buffer
information and transactions.

5. DataSet.RemotingFormatProperty:

When DataSet.RemotingFormat is set to
binary, the Dataset is serialized in binary format instead
of XML tagged format, which improves the performance of
serialization and deserialization operations significantly

6. Data Table’s Load and Save Methods:

In this Load method can load data
from objects such as XML in to Database objects and can
save them into the persistent data

7. New Controls:

DataGridView, Data Navigator, Data
Connector.

>inbuild webserver ... no need for iis(which is required in 1.0)
>master pages
> themes and skins,
> navigation controls
>login controls
>datasource controls (now gridview with added features when compared to datagrid in 1.0)
>webparts and also some techniques like improved caching techniques, cross page
>partial class,generics
>page directive include additional attributes

Net Framework1.0: -

This is the initial version of Microsoft .NET Framework.

************
.Net Framework 1.1: -

This is the major upgrade to the .NET Framework 1.0 to provide:

1) .NET Compact Framework - a version of the .NET Framework for small devices
2) Internet Protocol version 6 (IPv6) support
3) Built-in support for ODBC and Oracle databases: previously available as an add-on for .NET Framework 1.0, now part of the framework
4) Built-in support for mobile ASP.NET controls: previously available as an add-on for .NET Framework, now part of the framework
5) Security changes: enable Windows Forms assemblies to execute in a semi-trusted manner from the Internet and enable Code Access Security in ASP.NET applications
6) Numerous API changes and many more

************
.Net Framework 2.0: -

This version shipped with Microsoft Windows Server 2003 Release Candidate [RC]. This is the last version with support for Microsoft Windows 2000.

Changes in .NET Framework since 1.1:

1) Full 64-bit support for both the x64 and the IA64 hardware platforms.
2) Language support for Generics built directly into the .NET CLR.
3) Many additional and improved ASP.NET web controls.
4) New data controls with declarative data binding.
5) New personalization features for ASP.NET, such as support for themes, skins and webparts.
6) Numerous API changes and many more.

Differences Between Shadowing and Overriding

When you define a class that inherits from a base class, you sometimes want to redefine one or more of the base class elements in the derived class. Shadowing and overriding are both available for this purpose.
Shadowing and overriding are both used when a derived class inherits from a base class, and both redefine one declared element with another. But there are significant differences between the two.

1 The calling sequence consists of the element type (Function, Sub, Operator, or Property), name, parameter list, and return type. You cannot override a procedure with a property, or the other way around. You cannot override one kind of procedure (Function, Sub, or Operator) with another kind.

2 If you do not specify either Shadows or Overrides, the compiler issues a warning message to help you be sure which kind of redefinition you want to use. If you ignore the warning, the shadowing mechanism is used.

3 If the shadowing element is inaccessible in a further derived class, shadowing is not inherited. For example, if you declare the shadowing element as Private, a class deriving from your derived class inherits the original element instead of the shadowing element.

Authentication in ASP.NET

The .NET Framework uses role-based security and code-based security mechanisms for protecting resources and code from unauthorized use.

Role-based security
Code-based security

in the Core Security Concepts in .NET

The common language runtime (CLR) and .NET Framework provide many useful classes and services that enable developers to easily write secure code and system administrators to customize access to protected resources. The CLR and .NET Framework provide classes and services that implement these basic underlying concepts, including:
· Principals
· Permissions
· Security policies
· Authentication
· Authorization

ASP.NET authentication methods contain the code that is necessary to authenticate the user’s credentials. ASP.NET supports three types of authentication methods. These are
1.Windows-based authentication
2.Forms-based authentication
3.Microsoft Passport authentication

1.---- With Windows-based authentication, the ASP.NET Web application relies on the Windows operating system to authenticate the user. ASP.NET uses Windows-based authentication in conjunction with IIS authentication.
With Windows-based authentication, the user requests a secure Web page from the Web application, and the request then goes through IIS. If the user’s credentials do not match those of an authorized user, IIS rejects the request. The user then has to enter his or her name and password into the logon form. The credentials are again verified by IIS. If correct, IIS directs the original request to the Web application. The secure Web page is then returned to the user
2.------ Forms-based authentication refers to a system where non-authenticated requests are redirected to a Hypertext Markup Language (HTML) form by using Hypertext Transfer Protocol (HTTP) client-side redirection. The user provides credentials and submits the form. If the application validates the credentials on the form, the system issues an authentication cookie to the user. Subsequent requests from the user are issued with the authentication cookie in the request headers, and then the user is authenticated based on those request headers.

3.---- Microsoft Passport authentication is a centralized authentication service that offers a single logon option and core profile services for member sites. Users who sign up to use Passport are authenticated for access to Web sites through a single Passport account. Microsoft Passport is an XML Web service, and it is an integral part of the .NET Framework