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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...using multiple databases with DNNusing multiple databases with DNN
Previous
 
Next
New Post
8/29/2006 12:09 PM
 

Hello,

 i'm starting a new project for a client and would like to use DotNetNuke as a framework but i have some questions that remains unanswered. Was wondering if some experienced user would share some advice with me. BTW im new to DNN :)

1- My data is allready stored in a database different than the one used by DNN. I would like to use DNN for handling users, roles, memberships and devellop new modules to handle my existing data. When i look at module creation, i always see a ModuleId. Is this moduleId requirred? Let's say for example a have a table in my existing database with job offers and i want to create a module for allowing users to view, create, modify,... offers, but I don't keep the moduleId in my offers table. Offers will be displayed depending on the user role and not on the moduleId. What is the correct way of doing this?

2- I'm using LLBLGen as my persitent layer and have my own business layer. I would be very interrested in having some advice from experienced users using DNN and LLBLGen for creating modules.

 

thanks in advance for your time.

Mateo

 
New Post
8/29/2006 1:06 PM
 
the PortalID and ModuleID parameters that you see are for security and separation purposes, soo multiple modules can all put their content in 1 table, separated from eachother by the moduleID in the SQL

that's good practise but you do not need it

the same goes for CBO, It's good practise to use it, but you do not have to.

regarding LLBLGen, forget about DNN's DAL, just use your LLBLGen classes in the BLL of your module (you will have 2 BLL layers, but thats ok)
Its good practice in DNN4 to return a generic list from your BLL, but once again you do not need to, you could return a datatable or an arraylist


DNN is full of good practises so it's good if you copy the style, but you do not need to. DNN is just as flexible as regular ASP.NET so you are free to do as you like.

The only thing you need to remember is: "The better you follow DNN good practises, the less work you will have to perform upgrades in the future" you determine yourself how important this is





Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...using multiple databases with DNNusing multiple databases with DNN


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