Hello, I am trying to write my first module in DotNetNuke using DotNetNuke Community Edition 5.  I have never used DotNetNuke, however I am very experienced with SharePoint, and ASP.NET development.  I am having trouble understanding where to store data.  For example in SharePoint if I were developing a "Granite Picker" I would create a List and have a content type or two and store all my information in SharePoint Lists.  If ASP.NET, I would store everything in SQL however I would loose the productivity of the portal.  In DotNetNuke when writing a module to say... store information regarding a granite such as 3 different sized images for display, names, location of quary where would a good DotNetNuke store this data?  Everything I have read points to just creating tables, and stored procs like it was a stand-alone website and just have the module talk to them.  That seems to bypass any content management though so I wanted to get the opinions of all the experts on here.  Thanks for helping a newbie get up to speed on DotNetNuke development. 

 

Thanks Chris. I don't want to "recreate" anything, I want to use DotNetNuke in a manner that is considered Industry Standard practice. You said 99% of the time, people use their own access and storage, that sounds like the way to go then. :-) Thank you so much for getting back to me. In the SharePoint world i am so use to using the internal storage... Create a content type, then a custom list... I just wanted to make sure I wasn't missing something, and should be doing the same in DNN. Doesn't sound like I did though. Thanks again!