I have built an application for another company that basically allows users to submit photos for an event and then administrators go back and review the photos.
I'm having major problems in that it seems when more than one user is trying to upload a picture they must be using the same shared resource because it messes up the upload. The upload page is the only one I know for sure has a shared memory problem. Basically the page builds a session object that contains all the photo information they are posting to the server. When they finally post the images then it updates the server and uploads the images.
I don't know what I'm doing wrong, I thought that session vars would keep unique information for each user. I do also use viewstate, and I don't know if that's a problem. Previously I had used static variables to handle multiple postbacks to the same page but I thought they were causing the problem. So basically I use one big session object (containing a sorted list and dataset) that I maintain until the page is submitted. In between there are multiple steps where I have to postback to the server.
I really had no idea that the app would do this, I thought .NET created unique threads for each user but evidentally I'm doing something wrong. I need help immediately, preferrably someone I can talk to on the phone if needed. I've got the site published on a test server that I can show the winning bidder.
Attached I have the cs file and aspx file of the upload page. I am not the greatest asp.net programmer so forgive my code.
Please I only want ASP.NET guru who have handled this problem before, I don't have time to hire someone to "figure it out". Thanks!