Hi. I haven't used LINQ to SQL in any of my modules (although I have considered it). It would probably be faster in performance as well as development since you don't really need to write a dataProvider for sql from the ground up unless you wanted to include dataProvider validation before/after sending it to the database. It is something I might consider using down the line here. The main issue is that the objectQualifier setting in web.config wouldn't be honored by linq to sql classes and would prevent you from ever installing more than 1 DNN installation in the same database. Some people might not care about this since they are only going to use a single install anyways, but I would always play it safe and code for the possibility anyways. There is a dnn linq to sql adaptor somewhere on codeplex. If you want to read more, go to this website: http://dotnetnuke.adefwebserver.com/DotNetNuke/tabid/195/Default.aspx and look for the section called "Connecting your module to the database". It covers linq and the dnn linq adaptor. My only problem is sending a custom object like a Headline, Event, Venue or Testimonial through the linq to sql class methods. Guess I will have to expirament and see how complex it will get.

The objectQualifier is only used to separate multiple instances of DNN in a single database. It is mainly used to support shared hosting environments where you are given a single SQL database to work with. It is not required for a single installation of DNN or if you use separate databases in SQL server.

If you are developing modules for others, especially for sale, you should support objectQualifier in all of your code..

I hope this is of some help to you.