Hi All,

I have one simple question, why we cannot (not recommended by DNN) use Session variables in DNN?

I am stuck up in persisting the data between the pages.

One way I have seen is UserInfo class which is good example but its added as a property in PortalModuleBase. And we have decided not to touch DNN's core library.

Is there any good way to send the data between the pages and change it when user changes it.

e.g.

If I have a page called Employee List and there I have a gridview with employee listing as 1st column with HyperLink. When user clicks on that page it will go to Employee Details page and then on ward it will also move to some other pages like Employee Address Details, Employee Family Details etc. Now, when I traverse from these pages I should have EmployeeId, EmployeeName etc. available on that pages modules. How can I acheive this?

Thanks & Regards,

Deepak Khopade

There isn't a DNN specific reason to avoid Session variables, DNN is just relaying the industry mantra of 'Session variables are bad'.  There are a lot of good reasons NOT to use Session variables, and you should avoid their use as much as possible. Not to say they are not useful in certain circumstances.  If you want to use Session variables, go ahead, just be aware of the Pros and Cons of doing so...

http://www.4guysfromrolla.com/webtech/092098-2.shtml#postadlink

Hi All,

Thanks for your replies.

Thanks Steve, thet 4Guys link is very usefull.