I have several applications that are written in ASP and one application written in ASP.NET. Each app is stored in its own directory.
Both the ASP and .NET apps use session variables for logging in. I managed to pass the information to the .NET app in order to reset the variables when a person goes from the ASP app to the .NET app. This code is stored in the .NET directory in the global.asax file:
The problem I'm running into is that users are leaving the application open for long periods of time and the session variable is timing out, thus throwing an error when they try to do something.
I've tried setting the server timeouts to a high number, but I'm not sure if I set the right thing. Does anyone know what settings I need to tweak to raise the timeout of the session variable? Does the timeout for the website cascade from the top to all directories? Is it possible to set the timeout separately for the main directory and the subdirectory for the .NET application?
Both the ASP and .NET apps use session variables for logging in. I managed to pass the information to the .NET app in order to reset the variables when a person goes from the ASP app to the .NET app. This code is stored in the .NET directory in the global.asax file:
Code:
void Session_Start(object sender, EventArgs e)
{
// Code that runs when a new session is started
Session["UserID"] = Request.Form["UserID"];
}
The problem I'm running into is that users are leaving the application open for long periods of time and the session variable is timing out, thus throwing an error when they try to do something.
I've tried setting the server timeouts to a high number, but I'm not sure if I set the right thing. Does anyone know what settings I need to tweak to raise the timeout of the session variable? Does the timeout for the website cascade from the top to all directories? Is it possible to set the timeout separately for the main directory and the subdirectory for the .NET application?