ASP.NET + C# HttpContext.Current.Session is null (Inside WebService)
this is how I initiate the session
this is how I initiate the session
I am building a class to store User ID and User Role in a session. I’m not sure how this class will behave when multiple users are on the site at the same time. Does anyone see a problem with this?
We have a multi-layered Asp.NET Web Forms application. The data layer has a class called DataAccess which impements IDisposable and has an instance of our Entity Framework Object Context as a private field. The class has a number of public methods returning various collections of Entities and will dispose its Object Context when it is disposed.
I need a way to tell ASP.NET “Kill the current session and start over with a brand new one” before/after a redirect to a page.
Should dynamic business objects for a site be stored in the users session or use ASP.Net caching (objects such as orders, profile information etc)?
What are the exact steps required for a cookie to persist after a browser is closed? At the moment I have:
I am building a Asp.net Application. I need to save a HashTable in a session.
Can I use static variables in my web application ? what are the alternatives to static ? When I use static variables in pages and more than one user use the application, it makes conflict data (incorrect data).
I’d like to find out what session ID hijacking protection is built into the current version of ASP.NET.
I’m trying to determine if a Session variable exists, but I’m getting the error: