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.0DNN DAL - do I really need it?DNN DAL - do I really need it?
Previous
 
Next
New Post
3/23/2006 4:36 PM
 
I'm working as a consultant doing sofware development, mostly web projects these days, and so have been for the last 15 year. DotNetNuke is my prefered option whenever possible simply because it is a great "product" and it helps me with what is most important in my line of work, rapid development. Being a "dotnet nuker:er" I have always tried to conform 100% to the DotNetNuke way, including the usage of the DNN DAL, but now I am more and more starting to question the later.Also, I feel that the arraylist format used isnt really optimal from a productivity point of view, compared to using DataSets etc.
 
Please note that I am not really questioning the DNN DAL, I am more trying to figure out if it is really worth the extra work for me. As I pointed out early in my post, the key to success in my line of work is RAPID DEVELOPMENT, so if I do something that takes more time, I need to know it is worth it. Also please note that most of the applications I am involved in kind of normal small- and midsize applications, with no extreme requirements from a performance etc. point of view.
 
What is your opinions about this? What is your real life experiences? Have you tried any other way than the DNN DAL and expereinced problems? Am I correct to assume that from a DotNetNuke perspective, ie integration with the DotNetNuke framework, it really doesnt make any difference? Is it really worth spending hour after hour writing the DAL the DNN way (even with the help of CodeSmith etc) compared to just drop a few components in visual studio and completing a few wizards? What actual advantages do I get from using the DNN DAL rather than using the standard components available in Visual Studio 2005?
 
/pJ
 
PS For those of you who dont know, DAL = Data access layer...
 
New Post
3/23/2006 5:06 PM
 

The DAL is a best practice not a requirement. Frequently I code quick modules using direct datasource access, usually I use the DAAB to speed development. In some cases, using the DAL is not worth the effort e.g. I have a module that exposes sql server logs, and sql agent job status, I'm never going to make a version for another datasource so it made no sense to spend the extra time.

In the next version, we're adding some generic methods to speed development, you can read about it here . Realistically use of the DAL is sensible if you wish to sell your modules, or provide more flexibility for your customers, as using it will simplify the addition of other providers. At present I only know of an oracle provider, but there is a firebird one being developed  by the core, and I expect a mysql one to be developed in the near future.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/23/2006 5:37 PM
 
cathal wrote

The DAL is a best practice not a requirement. Frequently I code quick modules using direct datasource access, usually I use the DAAB to speed development. In some cases, using the DAL is not worth the effort e.g. I have a module that exposes sql server logs, and sql agent job status, I'm never going to make a version for another datasource so it made no sense to spend the extra time.

In the next version, we're adding some generic methods to speed development, you can read about it here . Realistically use of the DAL is sensible if you wish to sell your modules, or provide more flexibility for your customers, as using it will simplify the addition of other providers. At present I only know of an oracle provider, but there is a firebird one being developed  by the core, and I expect a mysql one to be developed in the near future

 
If I read between the lines in your post, I sense that what you are saying is kind of the conclusion I have drawn...unless you plan to distribute/sell your modules or is desperate for flexibility, don't bother using the DNN DAL. It will probably work fine, but the extra time you have to put into it wont really give you anything unless you need one or both the of the requirements listed above. If you are actually doing modules with the intent to either sell them or distribute them in any way outside the system they were built in, then it all starts making sense to use the DNN DAL as it will make your module more robust and increase the chance that it will be usefull in an unknown environment.
 
Or am I pushing it to much here?
 
/pJ
 
 
 
 
 
New Post
3/23/2006 6:54 PM
 

no, thats quite correct. I often also prototype modules using direct datasource access, and only convert them to DAL based modules when I have time. At the end of the day, we hope to encourage best practices as they maximise flexibility and reuse, but it's up to you to decide what best suits for your site/customer.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/24/2006 3:50 AM
 
cathal wrote

no, thats quite correct. I often also prototype modules using direct datasource access, and only convert them to DAL based modules when I have time. At the end of the day, we hope to encourage best practices as they maximise flexibility and reuse, but it's up to you to decide what best suits for your site/customer.

Cathal

 
OK, thanks for the input. You have confirmed my original thoughts here so I will defenitly consider the fast road for my future module development, when the requirements are not such that I need the portability or flexibility. I like it that the Nuke offers you different options, but dont force you to do things the Nuke way. DotNetNuke is simply great!
 
Any idea of when 4.1 with the new DAL will be available?
 
/pJ
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN DAL - do I really need it?DNN DAL - do I really need it?


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