About .NET Framework
http://en.wikipedia.org/wiki/.NET_Framework
The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime. The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL.
The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework.[10] It includes an expanded set of libraries, including WinForms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others
Difference between Abstract Class and Interfaces
An abstract class is a class that can not be instantiated but that can contain code. An interface only contains method definitions but does not contain any code. With an interface, you need to implement all the methods defined in the interface.
If you have logic that will be the same for all the derived classes, it is best to go for a abstract class in stead of an interface.
You can implement multiple interfaces but only inherit from one class.
Differences between the GridView control and the DataGrid control include:
1.Different custom-paging support.
2.Different event models.
DataReader v/s DataAdapter
Data Reader read only forward only. It's connection oriented. One should explicitly close the connection.
Data Adapter is disconnected. It's acts as a bridge between data set and database.
DataGrid Code
http://www.codersource.net/asp_net_datagrid_part1_azam.html
Grid view control in ASP .Net 2.0
http://www.codersource.net/asp_net_gridviewcontrol.aspx
Garbage Collection
The .NET Framework's garbage collector manages the allocation and release of memory for your application. Each time you use the newoperator to create an object, the runtime allocates memory for the object from the managed heap. As long as address space is available in the managed heap, the runtime continues to allocate space for new objects. However, memory is not infinite. Eventually the garbage collector must perform a collection in order to free some memory. The garbage collector's optimizing engine determines the best time to perform a collection, based upon the allocations being made. When the garbage collector performs a collection, it checks for objects in the managed heap that are no longer being used by the application and performs the necessary operations to reclaim their memory.
This section describes how the garbage collector automatically manages the allocation and release of memory for the managed objects in your application. In addition, it describes the recommended design pattern to use to properly clean up any unmanaged resources that your application creates.
Page Life Cycle
http://blogs.clearscreen.com/dtax/files/aspNET_Page_LifeCycle.jpg
http://en.wikipedia.org/wiki/.NET_Framework
The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime. The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL.
The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework.[10] It includes an expanded set of libraries, including WinForms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others
Difference between Abstract Class and Interfaces
An abstract class is a class that can not be instantiated but that can contain code. An interface only contains method definitions but does not contain any code. With an interface, you need to implement all the methods defined in the interface.
If you have logic that will be the same for all the derived classes, it is best to go for a abstract class in stead of an interface.
You can implement multiple interfaces but only inherit from one class.
Differences between the GridView control and the DataGrid control include:
1.Different custom-paging support.
2.Different event models.
DataReader v/s DataAdapter
Data Reader read only forward only. It's connection oriented. One should explicitly close the connection.
Data Adapter is disconnected. It's acts as a bridge between data set and database.
DataGrid Code
http://www.codersource.net/asp_net_datagrid_part1_azam.html
Grid view control in ASP .Net 2.0
http://www.codersource.net/asp_net_gridviewcontrol.aspx
Garbage Collection
The .NET Framework's garbage collector manages the allocation and release of memory for your application. Each time you use the newoperator to create an object, the runtime allocates memory for the object from the managed heap. As long as address space is available in the managed heap, the runtime continues to allocate space for new objects. However, memory is not infinite. Eventually the garbage collector must perform a collection in order to free some memory. The garbage collector's optimizing engine determines the best time to perform a collection, based upon the allocations being made. When the garbage collector performs a collection, it checks for objects in the managed heap that are no longer being used by the application and performs the necessary operations to reclaim their memory.
This section describes how the garbage collector automatically manages the allocation and release of memory for the managed objects in your application. In addition, it describes the recommended design pattern to use to properly clean up any unmanaged resources that your application creates.
Page Life Cycle
http://blogs.clearscreen.com/dtax/files/aspNET_Page_LifeCycle.jpg
