Httpcontext.Current.Session vs Session

saurabh

9y33.9k.NET

what is diffenrece between HttpContext.Current.Seesion and Session?

and if HttpContext is recreated during every new request and destroyed after response then how values stored in the session of HttpContext remains intact during the whole session of a

user (Means a single a session may involve many request then how values in the Session is intact and accessible during different request of a single session)...

thanks in advance.............

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Bikesh Srivastava9y ago
They're effectively the same, in that they will access the same Session data.
The reason you can call Session in your code-behind is because ASP.Net pages by default extend the System.Web.UI.Page type. This has a Session public property. If you look at the code for this in Reflector you can see that it just calls HttpContext.Current.Session itself (through its own Contextproperty).
In other classes you will not have access to that property, but you can use HttpContext.Current.Session to access the session data instead, as long as you're running in the context of a web application
0
Midhun Tp9y ago
Hi,

As per my knowledge, there is no difference between them. They both are same.

Please check below thread -

http://stackoverflow.com/questions/7954844/what-is-the-difference-between-these-two-httpcontext-current-session-and-session
0
Mangesh G9y ago
Hey saurabh

Actually these 2 are different

HttpApplication's Session property exhibits different behaviour than does that of the property HttpContext.Current.Session. They will both return a reference to the same HttpSessionState instance if one is available. They differ in what they do when there is no instance of HttpSessionState available for the current request.
Not all HttpHandlers provide session state. To do so, the HttpHandler must implement [one or both?] the marker interfaces IRequiresSessionState or IReadOnlySessionState.

HttpContext.Current.Session simply returns null if there is no session available.

The HttpApplication's implementation of the Session property throws an HttpException with the message Session state is not available in this context. rather than return a null reference.

Some examples of HttpHandlers that do not implement session are the the default handlers for normally static resources, such as image and CSS files. Any reference to the HttpApplication's Session property in such cases (as in global.asax event handlers) will result an HttpException being thrown.
For Reference try this

http://stackoverflow.com/questions/940742/difference-between-session-and-httpcontext-current-session

Mark Approved if it helps
0