state-server

Managing Session State

I have a need to maintain the session state in the database. However I cannot access the database directly from the web server. The web server communicates with an app server which in turn has access to the database. Is there a way to configure this? Or does a custom component have to be written. The reason for this setup is to allow ...

Upgrade from .NET 3.0 to 3.5: Sites set to StateServer revert to InProc when in Web Garden

Scenario: Take a server running .NET 3.0 and an ASP.NET Web site running in an application pool that has Web gardens enabled (number of processes: 3). The web.config configuration is as follows: <sessionState cookieless="UseCookies" cookieName=".authz" mode="StateServer" regenerateExpiredSessionId="true" ...

best way to share "session state" type data between two .net applications

Hi, we have a web application that, started out small, any new features that were added on, were just made as part of the same project, however now we would like to create new projects for these said addons... we created a new project, it inharits the global.asax of the main project, and also accesses the web.config of the main project ...

How to avoid single point of failure when using state server in ASP.NET website

In my current project, we have to create a website (ASP.NET MVC) which is likely to have sufficient load to demand a server farm. I understand that if server farm is used, session states must be stored on somewhere else such as SQL server database or state server. After some experimentation, we are inclined to use the state server mecha...

Preserve ASP.NET InProc Session when W3WP (IIS) Process Recycles

Hello, I understand that all InProc session data is always gone when its w3wp owner process recycles as it only resides in the w3wp memory. I wondered though if it is possible to cache the session data when recycling happens somewhere external to the process, and then reinject (and rebuild) the session when it comes back up. That way I...

Is ASP.Net State Server an elegant solution?

We have an ASP.Net MVC project that will start with a single web server but will likely soon scale into a small web farm. As ASP.Net Authentication stores a UserID, and data caching may also be useful, we will likely need to make the jump to state server fairly soon. I'd like to hear from others how State Server has been to work with...