Posted on 2003-10-22
I'm going through a pretty typical transition these days: I have a large intranet chock-full of Classic ASP applications, and i'm now writing much nicer apps in ASP.NET with C#. The problem of course is that ASP and the ASP.NET Process do not share a Session object. Fortunately I'm having no problem sharing information between the two, i'm just coming up with an unusual bug and I'm not sure how to fix it.
When a user logs in to the intranet, the ASP Session receives their user ID and a couple of other tiny variables. The ASP code that does that then forwards to an ASP.NET page that puts the same information into the ASP.NET Session. So far so good.
I've found that the ASP.NET session keeps expiring if the user isn't browsing ASPX pages. A user who spends 20 mintes (the current timeout) in a Classic ASP application will receive an error when they try to use an ASP.NET application because their User ID has disappeared from the ASP.NET session.
It was my impression that Session State would be preserved even if the user were browsing .HTML pages. Any experts have a clue to what's going on here? Your help is appreciated.