First of all to give you a bit of background on the current environment. We have a number of ASP.NET applications, all of which use session for certain aspects. We are “Load Balanced” over multiple servers due to traffic levels, however, our load balancing is set to use “Sticky Sessions” as currently all web applications are set to use “InProc” for session state.
i’m trying to store some values in the Session from a Handler page, before i do a redirect to a WebForms page, that will pick up the Session values and pre-fill the WebForm: public class Handler : IHttpHandler { public void ProcessRequest(HttpContext context) { … context.Session["StackOverflow"] = "overflowing"; context.Response.Redirect("~/AnotherPage.aspx"); … } … } Except context.Session … Read more
I have built a shopping cart that uses Session State to keep the shopping cart data while the user is browsing the store.
I see two means of working with session data in ASP.NET MVC:
What is the difference between IRequiresSessionState and IReadOnlySessionState beside the inability of the second to save changes to the session variables?
I need to understand something about ASP.NET session state, as it applies to IIS 7 and ASP.net 3.5.
Recently, while working on some code for an ASP.NET project at work. We needed a tracking util to take basic metrics on user activity (page hit count etc) we would track them in Session, then save the data to DB via Session_End in Global.asax.
I have an ASMX webservice hosted alongside my ASP.NET web app. Now, I need to get the users session into the Webservice. To test this I made this simple method:
We are migrating an ASP Classic website over to ASP.Net. One of the big hurdles is the large amount of data stored in SessionState by the ASP Classic website.
I’m using ASP.NET’s in-process session state store. It locks access to a session exclusively, and which means concurrent requests to the same session are served sequentially.