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.0Using Existing projects with DNN 4.x module creationUsing Existing projects with DNN 4.x module creation
Previous
 
Next
New Post
3/14/2007 3:55 PM
 
Hello, I am brainstorming something for a project I am working on:

Suppose I have created an API for a website that I would now like to use in a new module for DNN.  In the current model, there is a section to include the database execution.  Because I have this API that already connects to its own database, I feel that I do not need this layer.  I would however like to use the power of DNN to create my modules. 

My question to any developers down this path, what do you think the best practice is for this problem?  I could simply bypass the database layer, but I feel that it would be considered bad practice and I may be missing in some of the features that DNN has to offer.

I am willing to create a database adapter for my API to plug into the DNN model, but I do not want to recreate the API, because it defeats the purpose of rewriting the code.  Anyone else have any issues with something like this?  Any help or just ideas would be greatly appreciated.

Thanks,
M Doyle
 
New Post
3/14/2007 11:45 PM
 

Seems to me - it really comes down to what you want to do with the modules you are building.

What the DAL really does in DNN is provide a mechanism to abstract access to the database and provide object hydration tools.

If you have your own data access API then for your own purposes - you may as well continue to use it for accessing your own data structures.

I guess the only reason you would not - was if you were planning on delivering the module as a commercial product and you wanted to allow for future connect to DAL supported data providers in the future

 

 
New Post
3/15/2007 12:29 AM
 

If you use the DAL+ it will require less code than if you used your own DAL

see:

DAL & DAL+ &

Use DAL+ ExecuteSQL for truly rapid DotNetNuke® Module development



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
3/15/2007 1:03 AM
 

One if the really cool things about the DAL+ concept is that you are only working with one file for all your data access routines ...

Under the DAL system you are fighting with multiple classes spread across multiple files - which greatly increase the debug - typo cycle.

In large multi module projects - these days I often put all the userinfo definitions in one .vb container and the controller code in a second .vb container - the result is a one stop shop for all data access needs.

Westa

 
New Post
3/16/2007 9:16 AM
 
thanks for your info guys, I will look into these solutions.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using Existing projects with DNN 4.x module creationUsing Existing projects with DNN 4.x module creation


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