jit is stands for just in time compiler
in case of compilation 
source code ->language compiler->MSIL->JIT->native\machine 
code

in case of compilation the source code is compiled by its 
language compiler like in case of vb.net it is compiled by 
its lanfuage comiler and then convert it in MSIL which jit 
can understand and then jit compile itand convert it in 
machine code
types of jit
1)pre-jit
   it compile all methods at one time compilation
2)econo-jit
   it compile only those methods which are cslled at run 
time
3)normal jit
 it compile only those methods which are called at run time 
and the mthods which are compiled at one time that is kept 
in cache and next time when that need it tack from cache

MSIL,IL is same i.e All .net source code compiled to MSIL.
CTS means it is a set of type definations

MSIL is Microsoft Intermediate Language, whtever code 
written in .net is complied into an intermediate native 
language and this language is called MSIL, this language ia 
again complied into low level intermediate lamguage called 
Just In Time Compiler. 

CTS is Common Type System that defines how variables, 
methods are decalred & how object are defined & used

CLR means common Language runtime. Which is Engine of .net 
Platform. Which is responsible for execution of code, cross 
Language interoperability, garbage Collection, Security, 
Exception Handling.

Common language runtime(CLR) which enables dotnet to accept 
many language like vb,c#,java etc,Any language inwhich we 
are writting the code must comply with CLR and then it will 
send to Microsoft intermediate language(MSIL) it will 
compile and convert the language into managed code since 
managed code is the only language known to .net compiler 
its easy to use any compatible language in dotnet cross 
language interoperability,security,execption handling also 
possible only because of CLR.

Native Support for Developing Mobile Web Applications 
 Enable Execution of Windows Forms Assemblies Originating 
from the Internet

Answer It?s both and actually a lot more. Microsoft .NET is 
a company-wide initiative. It includes a new way of 
delivering software and services to businesses and 
consumers. A part of Microsoft.NET is the .NET Frameworks. 
The frameworks is the first part of the MS.NET initiate to 
ship and it was given out to attendees at the PDC in July. 
The .NET frameworks consists of two parts: the .NET common 
language runtime and the .NET class library. These two 
components are packaged together into the .NET Frameworks 
SDK which will be available for free download from 
Microsoft?s MSDN web site later this month. In addition, 
the SDK also includes command-line compilers for C#, C++, 
JScript, and VB. You use these compilers to build 
applications and components. These components require the 
runtime to execute so this is a development platform. When 
Visual Studio.NET ships, it will include the .NET SDK and a 
GUI editor, wizards, tools, and a slew of other things. 
However, Visual Studio.NET is NOT required to build .NET 
applications.

In simple it is both runtime service and a development 
platform.

It is set of languages which are integrted in to a single 
and design power ful application irrespedtive of language.

A programming infrastructure created by Microsoft for
building, deploying, and running applications and services
that use .NET technologies, such as desktop applications and
Web services.

The .NET Framework contains three major parts:

    * the Common Language Runtime
    * the Framework Class Library
    * ASP.NET.

ado.net is xml based and ado is com based 
here easy to implement he disconnected model and diffcivult 
to

ADO.NET is stateless mechanism. I can treat the ADO.Net as a
separate in-memory database where in I can use relationships
between the tables and select insert and updates to the
database. I can update the actual database as a batch.

ADO : Needs contionous connection to read records.

ADO.NET : It reads entire results and keep it the form of 
table. So it never re-connect with DB.

The first data access model, DAO (data access model) was 
created for local databases with the built-in Jet engine 
which had performance and functionality issues. Next came 
RDO (Remote Data Object) and ADO (Active Data Object) which 
were designed for Client Server architectures but soon ADO 
took over RDO. ADO was a good architecture but as the 
language changes so is the technology. With ADO, all the 
data is contained in a recordset object which had problems 
when implemented on the network and penetrating firewalls. 
ADO was a connected data access, which means that when a 
connection to the database is established the connection 
remains open until the application is closed. Leaving the 
connection open for the lifetime of the application raises 
concerns about database security and network traffic. Also, 
as databases are becoming increasingly important and as 
they are serving more people, a connected data access model 
makes us think about its productivity. For example, an 
application with connected data access may do well when 
connected to two clients, the same may do poorly when 
connected to 10 and might be unusable when connected to 100 
or more. Also, open database connections use system 
resources to a maximum extent making the system performance 
less effective.

diff:
1.ADO is a connected approach,where as ADO.Net is a 
disconnected data approach.
2.ADO is a concept of vb 6.0,where as ADO.Net ia concept 
of .Netframework.
3.ADO is a Object Based,where as ADO.Net is a Object 
Oriented.
4.ADO supports recordset,whereas ADO.Net supports dataset.

1.ADO is a connected approach,where as ADO.Net is a 
disconnected data approach.
2.ADO is a concept of vb 6.0,where as ADO.Net ia concept 
of .Netframework.
3.ADO is a Object Based,where as ADO.Net is a Object 
Oriented.
4.ADO supports recordset,whereas ADO.Net supports dataset.

1.	Business Model


ADO is Connection-oriented Models used mostly
ADO.NET is Disconnected models are used:Message-like Models.


2.	Disconnected Access

ADO Provided by Record set.
ADO.NET Provided by Data Adapter and Data set

3.	XML Support

ADO Limited
ADO.NET Robust Support

4.	Connection Model 

ADO Client application needs to be connected always to
data-server while working on the data, unless using
client-side cursors or a disconnected Record set 

ADO.NET Client disconnected as soon as the data is
processed. DataSet is disconnected at all times.

5.	Data Passing 

ADO objects communicate in binary mode.
 ADO.NET uses XML for passing the data.

Using pagination option in DataGrid control. We have to set
the number of records for a page, then it takes care of
pagination by itself.

set allowpaging to true and you have to write some coding 
in pageindexchanging event

GridView1.PageIndex = e.NewPageIndex;
binddata();

Client side is done by default. Server side validation is
also possible. We can switch off the client side and server
side can be done.

Validation can be done both Server & Client Side..
among all the validatiors only Customer Validation is done 
at Server Side.. rest of them r done at Client side..

by setting the control to validate property in validator to 
that controler

we can validate controls either server side or client side. 
for client side vaildaions we can your either javascript or 
validation controls provided in .NET.

1)Page_Init
2)Page_load
3)page_prerender
4)page_unload

pre-init
init
init-complete
pre-load
load
load-complate
prerender
unload

The load view state stage only happens when the page has 
been posted back. During this stage, the view state data 
that had been saved from the previous page visit is loaded 
and recursively populated into the control hierarchy of the 
Page. It is during this stage that the view state is 
validated. The view state can become invalid due to a 
number of reasons, such as view state tampering, and 
injecting dynamic controls into the middle of the control 
hierarchy.

ViewState is the mechanism ASP.NET uses to keep track of 
server control state values that don’t otherwise post back 
as part of the HTTP form. ViewState Maintains the UI State 
of a Page
ViewState is base64-encoded. It is not encrypted but it can 
be encrypted by setting EnableViewStatMAC=”true” & setting 
the machineKey validation type to 3DES. If you want to NOT 
maintain the ViewState, include the directive < %@ Page 
EnableViewState="false" % > at the top of an .aspx page or 
add the attribute EnableViewState=”false” to any control.

view state is nothing but store all the current page 
informations and the control details when the page is 
postback.all the control details and values to be stored in 
hidden field.Those hidden fields are creating dynamically 
depending upon the page placed controls.If you want to 
fetch the values of the previous page control(ex:'Name' is 
the previous page control Id)

Get the value of name from second page

sample code:

string get_Name=viewstate["Name"].Tostring();

*Viewstate object is used to persist data of variables 
across postbacks.
*Viewstate object's value is accessible only at page level.
*This means that if a viewstate is created at MyPage.aspx, 
then it may be used only within MyPage.aspx after the 
postback, and cannot be used by any other page.

This is used to prevent the flickering of page when it load

A SmartNavigation is a property of the Page class in
System.Web.UI. When a request comes in to Internet Explorer
5.5 or higher and SmartNavigation is turned on (set to
true), the following actions are performed:

    * The flash caused by navigation is eliminated
    * The scroll position is persisted when moving from page
to page
    * Element focus is persisted between navigations
    * Only the last page state in the browser's history is
retained

Resource files are stored with culture extenstion in their 
name. System.Globalization.CultureInfo.CurrentCulture.Name 
is used to get the current culture name.

In case if asp.net new controlls are used like 
datagrid,dataset etc
In case of asp.net there is html code also for each control
where in asp not.

In asp.net ,separation of presentation and design logic(code
behind).

code is structured

if you want  to create a control,for example label or text
box  it takes simple coding.

These features are not available on asp

Microsoft's previous server side scripting technology ASP
(Active Server Pages) is now often called classic ASP. 
ASP 3.0 was the last version of the classic ASP.

ASP.NET is the next generation ASP, but it's not an upgraded
version of ASP. 
ASP.NET is an entirely new technology for server-side
scripting. It was written from the ground up and is not
backward compatible with classic ASP.

Differences between ASP and ASP.NET
_____________________________________
ASP.NET has better language support, a large set of new
controls and XML based components, and better user
authentication.
ASP.NET provides increased performance by running compiled code.
ASP.NET code is not fully backward compatible with ASP.
________________________________________
New in ASP.NET
	Better language support 
	Programmable controls 
	Event-driven programming 
	XML-based components 
	User authentication, with accounts and roles 
	Higher scalability 
	Increased performance - Compiled code 
	Easier configuration and deployment 
	Not fully ASP compatible 
        Ready Validators for validation even with custom
validator to let prgrmr write validation code on his own coding
________________________________________

Dot net is Platform independant,Language Neutral,Supports 
Window based and web based applications

Asp is not as above