Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0POST instead of GETPOST instead of GET
Previous
 
Next
New Post
3/25/2007 1:48 PM
 
1. You can put your value inside session

2. You can use Crosspage Postback and recover your value with PreviousPage property.
http://www.aspitalia.com/script/674/Effettuare-Postback-Pagina-ASP.NET-2.0.aspx

3. You can use delegate.

4. httphandlerfactory (Url Rewriting)
 
New Post
3/25/2007 3:25 PM
 

You can also use Personalization. see: Module Settings and Personalization: Easily Store Data for Your Module (VB &C#). Personalization will tie the values to the current user (which I am sure is what you want).  



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
3/26/2007 6:34 PM
 
Yes this is exactly what I was looking for ... Thanks!
 
New Post
3/28/2007 1:56 PM
 
This works great if the user is logged in ... what option is there for when they are not authenticated?  Would session be my only choice then?
 
New Post
3/28/2007 3:18 PM
 

Sybru:

Michael's excellent article covers two separate areas, Module Settings is one, Personalization is the other.  The Module Settings are related to a particular instance of the module, regardless of the user. or whether one is logged in.  By the way, you have not told us exactly what is the nature of the values you are talking about.  You have different options depending on what you need to accomplish.  Just remember that the Module Settings are not user related but permanent, Personalization is user related and also permanent.  Session is not user related and is not permanent.  You may want to consider these criteria when you decide the option to use.

By the way, Session variables are not a bad thing, you can use them without a problem, even in DNN.  What you do not want to do is to store big datasets in them for instance, specially in sites with a lot of concurrent users or in an underpowered server with limited memory.

Carlos

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0POST instead of GETPOST instead of GET


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out