Best approach for startup info

Jone

New member
Joined
Mar 14, 2006
Messages
2
Programming Experience
10+
In a straight ADO.NET application over a LAN what is the best way to persist startup information, such as user preferences, system rules and roles, for the length of a user session? Upon user login I initially read this data, but where do I store it? Should I save it in an object based on the Singleton pattern, and continually reference that persisted object for the length of the session?
 
Back
Top