stateserver

While deploying my application in azure i got this error when a session variable is used I know this error is due to ASP.Net state server mode . I started the service in my local PC but how to start this service in Azure environment? You can use a start up task to spin up the State Service (or really any service for that matter). However, I would highly recommend that you do not use the session state service. I'd recommend looking at the In Role Windows Azure Cache or the Windows Azure Cache Service (Preview) for session state. By using the session service you separate your session concerns

I have found a lot of great information comparing InProc, StateServer, and SQLServer for ASP.NET state management, but I can't seem find any performance benchmark comparisons. It is clear that InProc is faster than StateServer which in turn is faster than SQLServer, but it isn't clear how much faster. I realize that it's going to vary greatly by application and environment, but having a relative idea of how they compare would be valuable. Do you know of any benchmarks that have been performed that you could share? or have any personal experience with this? Thank you! There's a good benchmarks

Before I start using Session State server for the benefit of making session state more robust in my apps compared to InProc state, I'd like to find a list of Pros and Cons for evaluation. Update 1 : Also about surviving application pool recycles? Update 2 : What about longevity of sessions and their endings? Here's the canonical analysis of the pros and cons of your three options, from Rob Howard's ASP.NET Session State article: In process . In process will perform best because the session state memory is kept within the ASP.NET process. For Web applications hosted on a single server,

I'm having trouble getting 2 identical ASP.NET MVC applications to share the same Session using a Session StateServer. The reason I'm trying to do this is we will eventually be deploying this app across 3 web servers that need to share the same state. We need to use StateServer because we are trying to minimise use of the db for non data-related storage. The Setup: I've deployed the same code base to http://localhost/ App1 and http://localhost/ App2 both have identical Web.Config files with the following: <system.web> <sessionState mode="StateServer" cookieless="false" timeout="20"

I have two identical applications setup on IIS on different virtual directories (I have done some workaround to ensure that they both have the same application name). Is there a way to share session id across two asp.net web applications? Since I'm storing the session in StateServer, they should both be getting the same session data, however, a different session id is created everytime I go from application a to applicatino b. Wouldn't this happen in a load balancing scenario as well? Where when I go to www.test.com, it would redirect that request to server a, and then if I hit it again, it