What's the point of asp.net /dnn cache when you can save shared info as global variables in shared classes? Because you need to know that variables in user controls get cleared on every postback, but variables in shared classes persist.

Shared variables are better because 1. they would be a little faster than cache because cache needs to lookup dictionary. 2. they are more readable, easier to use

Am I missing something? Is there some trick with portals? if 2 portals use my module, will values in shared class variables be different in portals and same in cache?

 

Hi asp.net / dnn cache is designed to contain more data then variables.

If include also dependecy mechanisme, for clearing cache part when the cache becaumes to big or when the cache becaumes invalid (depending on time delais, file changes, ...).

---

Forge projects : Open Url Rewriter - Open Content - Open Form