Copying DLLs to your production server will have the same effect. I have some largeish websites setup using StateServer and haven't noticed any detrimental effect...and they are all using the same SQL Server (which is running the Session State Service).
I am sure you'll be fine - well as sure as one can be without seeing the details of your site and how you use session state - but it sounds pretty simple. --b Bryan Batchelder eBusiness Consultant ConnectWise, Inc. 813-935-7100 x 425 > -----Original Message----- > From: Houck, Rob [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 14, 2002 12:56 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] ASP.NET Session Expiration > > > Bryan, > > Good point. > > We're going live with the application in a couple of weeks, > and it currently hosts between 200-250 concurrent users (with > spikes to 500). I didn't want to be in a situation where > updating the production software would cause everyone to > loose their session.. :) > > Or.. Am I seeing something that only would occur on our > development servers (caused by the *build* operation) and > would not happen in production (caused by copying new DLL's > to the production box)? > > Rob > > -----Original Message----- > From: Bryan Batchelder [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 14, 2002 12:42 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] ASP.NET Session Expiration > > > I haven't noticed any detrimental affects from switching to > StateServer vs. InProc. > > You can always go back to InProc on your production machine, though. > > --b > > Bryan Batchelder > eBusiness Consultant > ConnectWise, Inc. > 813-935-7100 x 425 > > > > > -----Original Message----- > > From: Houck, Rob [mailto:[EMAIL PROTECTED]] > > Sent: Friday, June 14, 2002 12:08 PM > > To: [EMAIL PROTECTED] > > Subject: [DOTNET] ASP.NET Session Expiration > > > > > > Hi all, > > > > In doing some development, I noticed that every time I do a > build on > > our development server, any attached users loose their current > > session. I'm > > (obviously) using the default inproc session management. > > > > I believe I can simply use out of process session management to > > correct this behavior. Is this true? I manage a very small > amount of > > information in session (six integer values), so will out of process > > session management really have much of an impact on the > performance of > > my application? > > > > > > Rob > > > > ============================================================== > > ========== > > > > Robert L. Houck, Jr. > > Northshore Computer Solutions Chance favors the > prepared mind. > > http://www.northshores.com/ - Louis Pasteur > > 419.242.3696 ext. 401 > > ============================================================== > > ========== > > > > You can read messages from the DOTNET archive, unsubscribe from > > DOTNET, or subscribe to other DevelopMentor lists at > > http://discuss.develop.com. > > > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > > You can read messages from the > DOTNET archive, unsubscribe from DOTNET, or subscribe to > other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
