Hi.  I am using DNN framework  to build my web site.   I am at the point of learning and planning.   I have read many module development tutorials.  All of them indicate that I need to use ModuleID in the tables  as well as {objectQualifier} as good practice.   As I understand that usage of these practices is designed for modules that will be distributed to unknown environment with other modules as well as having ability to have multiple module on the site.

 In my case I am building Web site and all the modules will be solely used for my project and are not for redistribution.  I will not have any modules that will need to be added more than once. Also the most important is that most of my modules will be sharing some tables  and tables will not be only used by one module.  I was wondering if there is a real need to use ModuleID in the table and {objectQualifier}.   According to what I know so far about its purposes I do not need it,  but I might overlook something so please let me know.  I am just on a tight dead line so do not want to use what I do not have to but at the same time do not want to have problems later to have thing redone.   Also if I do use it  I am not sure how I can use it if the tables will be shared by several modules so I cannot really localize to certain module and set proper {objectQualifier} and ModuleID.  Any suggestions ??

Also, I am planning to use some base classes such as LINQ_SQL as well as other classes across entire application that will be shared by many modules on the portal. What is better practice to build a separate DLL and ad reference from DNN or just put al classes under APP_Code?? May be any other suggestions.

Thanks for suggestions and experience sharing.

I would suggest patience for starters. People have to digest your post and prepare a repsonse. Demanding replies is frowned upon and may be ignored. 

Dwayne,

Thanks for your post,  I did not mean to be persistent. I just know if post get burred and nobody response for few days it might just go unanswered.   Thank for your useful tips.  I am not trying to build modular application, I am just using DNN as framework but as I learned so far following bets practice and keep modular design is better.  The only thing is that  most my modules will share many DB tables as well as base classes and LINQ entities so I have to make it work somehow.  I was thinking to create separate base classes that would include LINQ db entities and the rest of the classes shared  by module and just reference to DLLs as well not using ModuleID and objectQualifiers.  is it common practice?