S.NoViewStateSessionState1View state is maintained in page level only.Session state is maintained in session level.2View state of one page is not visible in another page.i.e., when user requests another page previous page data will be no longer available.Session state value is available in all pages within a user session.i.e., The data will be no longer available if user close the browser or session timeout occurs.3
View state information stored in client only.Session state information stored in server.4View state persist the values of particular page in the client (browser) when post back operation done.Session state persist the data of particular user in the server. This data available till user close the browser or session time completes.5View state used to persist page-instance-specific data.Session state used to persist the user-specific data on the server side.
S.NoViewStateControlState1ViewState can be disabledControl State cannot be disabled.2ViewState is implemented by using EnableViewState property of a control to true.Control State works even when EnableViewState is off.To use Control State (for example in a custom control) we have to override OnInit method,call RegisterRequiresControlState method in OnInit method and then override the SaveControlState and LoadControlState methods.3
ViewState is used to maintain page-level state for large dataControl State is used for small data only.
eg: maintain clicked page number in a GridView even when EnableViewState is off
S.NoSessionStateCookies1Session can store any type of data because the value is of datatype of "object"Cookies can store only "string" datatype2These are stored at Server sideThey are stored at Client side3