Hi.

I've started creating my custom module.

I'm familiar with .NetTiers (http://nettiers.com/) DAL generator (CodeSmith template).
It generates v. good DAL, also with GetBy... methods  for foreign keys, indexes, ....  (not only for PKs).

So I used NetTiers for generating DAL. It works fine, but :
My generated DAL doesn't use DNN core API, for example :
- DotNetNuke.Framework.Reflection.CreateObject(...) in DataProvider
and so on.

My question is : Will caching mechanism work for such module with custom non DNN style DAL ?
I don't know details about caching in DNN, how it works, but for ex. this above method Reflection.CreateObject(...) (which I don't use) has one parameter CacheKey.
So I guess caching will not work, because my DAL is not 'registered' in DNN core API (or is not using it).

I tried it, I set caching for my module for ex.: 60 s., but my DAL is executed all the time.
But maybe its another issue, I don't know.

Second question :
What are other issues of using custom, non DNN style Data Access Layer ?

regards, Tomasz Modelski

Hi Tomasz,

I don't use the DNN DAL either, we generate ours with MyGeneration.  I'm not familiar with your data layer, but it sounds alot like mine.  You simply need to do your own caching.  For example in our digContest module, here is the code that gets a contest record:

        public DigContestRow GetContestRow( int contestID )
        {
            string key = "ContestRow" + contestID.ToString();
           
            DigContestRow row = (DigContestRow)DataCache.GetCache(key);
           
            if( row == null )
            {
                DigContestDB db = new DigContestDB();
                row = db.DigContest.GetByPrimaryKey(contestID);
                db.Close();
                if( row != null )
                    DataCache.SetCache(key, row );
            }

            return row;
        }

In my opinion, there is no advantage to using the DNN data layer.  It's a personal preference. 

Thanks,
Mike