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...