- Joined
- Jun 26, 2011
- Messages
- 1
- Reaction score
- 0
Hi all,
New to asp.net and I am working on a application where I created a seperate class in my application to hold property values(get, set) of user information as they log in. This information is used to be called from different web pages as needed to display information geared to that user. I set them up as Shared values. The problem is that as many users log into the application, the other users info is getting changed to the person that logs in next. My understanding was that if I declared something as Shared you would have only one copy of that and Shared throughout the application but each user would have their own instance of a session when acccessing the site so in essence they would get their own copy and wouldn't have an issue with concurrency. Can anyone explain to me where my logic is off and how I can fix this. I don't want to use Sessions for timeout issues and have run into issues with session before.
Thanks
New to asp.net and I am working on a application where I created a seperate class in my application to hold property values(get, set) of user information as they log in. This information is used to be called from different web pages as needed to display information geared to that user. I set them up as Shared values. The problem is that as many users log into the application, the other users info is getting changed to the person that logs in next. My understanding was that if I declared something as Shared you would have only one copy of that and Shared throughout the application but each user would have their own instance of a session when acccessing the site so in essence they would get their own copy and wouldn't have an issue with concurrency. Can anyone explain to me where my logic is off and how I can fix this. I don't want to use Sessions for timeout issues and have run into issues with session before.
Thanks
Last edited: