As has already been mentioned, depending on the size, yes, you'll see a
performance hit.
However, you can do this with smaller objects marked as serializable OR
wrap the individual session variables with a class, which is my
preference. This way, I end up working with typed session variables, I
don't have to remember what string I used for the key, and I get
intellisense on my session vars.
http://www.dmbcllc.com/Articles/WebD...8/Default.aspx
-----Original Message-----
From: guy [mailto:gu*@discussions.microsoft.com]
Posted At: Thursday, November 01, 2007 7:08 AM
Posted To: microsoft.public.dotnet.framework.aspnet
Conversation: Valid appraoch to State management?
Subject: Valid appraoch to State management?
Is this a valid approach to State Management?
What I do is define a class 'State' which holds all the objects etc. that
I
need to store in the Session.
I can then get my state object and reference all the objects that I need .
Later I can then save my state object back for use later.
This makes coding much simpler than storing individual items in the
session
state but is there a performance hit for working this way?
guy