Answer / krishnarao

StateManagement is a concept of maintaning the state
belonging into to the client.

StateManagement is 2 types

1.Client Side Statemanagement
A.View State
B.Query String
C.Hidden Fields
D.Cookies
2.Server side Statemenagement
A.Session
B.Application
C.Cache

Answer / srinivasa choudary.m

There are different techniques for ASP.NET State Management
1. View State
2. Cookies
3. Session
4. Cache
5. Application, Etc.,

Answer / shamna sankar

State management is implemented in order to retain
information about the user requests. Web pages are
stateless. Each request creates new page without retaining
any previous information about the user requests. ASP.NET
supports several State management techniques to maintain
state information.

State management in ASP.NET can be classified into
1.Client-side state management
2.Server-side state management

Client-side state management

This maintains information on the client's machine
using Cookies, View State, and Query Strings.

Cookies.
A cookie is a small text file on the client machine either
in the client's file system or memory of client browser
session. Cookies are not good for sensitive data. Moreover,
Cookies can be disabled on the browser. Thus, you can't
rely on cookies for state management.

View State
Each page and each control on the page has View State
property. This property allows automatic retention of page
and controls state between each trip to server. This means
control value is maintained between page postbacks.
Viewstate is implemented using _VIEWSTATE, a hidden form
field which gets created automatically on each page. You
can't transmit data to other page using view state.

Querystring
Querystring can maintain limited state information. Data
can be passed from one page to another with the URL but you
can send limited size of data with the URL. Most browsers
allow a limit of 255 characters on URL length.

Server-side state management
This kind of mechanism retains state in the server.

Application State
The data stored in an application object can be shared by
all the sessions of the application. The application object
stores data in the key value pair.

Session State
Session state stores session-specific information and the
information is visible within the session only. ASP.NET
creates unique sessionId for each session of the
application. SessionIDs are maintained either by an HTTP
cookie or a modified URL, as set in the application's
configuration settings. By default, SessionID values are
stored in a cookie.

Database
Database can be used to store large state information.
Database support is used in combination with cookies or
session state.

Answer / shamna sankar

State Management is 2 types

1.Client Side Statemanagement
A.View State
B.Query String
C.Hidden Fields
D.Cookies
2.Server side Statemenagement
A.Session state
B.Application state

Answer / sanjayi

the different techniques are
1. View State
2. Cookies
3. Session
4. Cache
5. Application, Etc.,

StateManagement is 2 types

1.Client Side Statemanagement
A.View State
B.Query String
C.Hidden Fields
D.Cookies
2.Server side Statemenagement
A.Session
B.Application
C.Cache

State management is implemented in order to retain
information about the user requests. Web pages are
stateless. Each request creates new page without retaining
any previous information about the user requests.

Answer / kamal sharma

StateManagement are 2 types

1.Client Side Statemanagement
A.View State
B.Query String
C.Hidden Fields
D.Cookies
2.Server side Statemenagement
A.Session
B.Application
C.Cache
d.profile

State management is implemented in order to retain
information about the user requests. Web pages are
stateless. Each request creates new page without retaining
any previous information about the user requests.

You are planning the deployment of an ASP.NET application. The application uses a Visual Studio .NET component named DataAccess that will be shared with other applications on your Web server. You are using Visual Studio .NET to create a Windows Installer package. You need to deploy DataAccess and the ASP.NET application so that they can be uninstalled later of necessary. What should you do? A . Create a setup project for DataAccess. Add the ASP.NET application in a custom action. B . Create a setup project for the ASP.NET application. Create another setup project for DataAccess. C . Create a Web setup project for the ASP.NET application. Add a project output for DataAccess. D . Create a Web setup project for the ASP.NET application. Add a merge module for DataAccess.

3 Answers   Syntax Softtech,

What r Callbacks in ASP.NET?

1 Answers  

In what order do the events of an ASPX page execute, As a developer is it important to understand these events?

4 Answers  

Explain Authentication mechanism in dotnet

0 Answers   BirlaSoft,

How can you provide an alternating color scheme in a Repeater control?

6 Answers   Siebel Systems,

Explain what does wsdl stand for?

0 Answers  

How to write test case (Unit test plan)

1 Answers   Syntel,

Types of caching. How to implement caching?

2 Answers   Microsoft,

Why session is necessary in web application?

0 Answers  

what is the difference b/w .net 1.1 and 2.0 ?

2 Answers   Polaris,

WHAT IS OBJECT POOLING

2 Answers   Fidelity,

Does asp.net still recognize the global.asa file?

0 Answers