I have several ASP.NET applications deployed in a farm of 4 Windows 2003 machines. Each application uses a separate App Pool and Virtual Directory in IIS. They rely heavily on sessions which are persisted out of process on a single SQL Server 2000 (<sessionstate mode="sqlserver" ... />). Applications are compiled against .NET 3.0 but .NET 3.5 SP1 is installed on servers.
What is the difference between these 2 piece of codes.
I am facing a problem. I have created two sessions:
I want to keep viewstate of a specific page in session but following code block does not help me, what might I be missing?
I’m asking this question out of curiosity.
Any advise on this one would be greatly appreciated, I’ve been researching all morning and I’m still scratching my head. I started at a new company a few weeks ago, where I’m the only .NET developer as the development was originally done by an outsourcing company and I’ve been asked to research.
My knowledge of the existing system is extremely limited but from what I can gather the situation is as follows.
I am looking for a reliable way to log out a user or abandon their session when the browser is closed. Is there a way to do this with tabbed browsers?? Any suggestions are appreciated. Thanks!
Is it possible to allow only one concurrent login per user in ASP.NET web application?
In ASP.NET if items are left in the session state that Implement IDisposable but are never specifically removed and disposed by the application when the session expires will Dispose be called on the objects that any code in Dipose() will execute?