Hi Brandon

I was able to get it work with creating a seperate LINQ library. The advantage/disadvantage is that it completely bypasses the Provider model that we use with the traditional DNN development. Personally I think I will use LINQ DBML for table related to my module only, but thats just me.

I will post a tutorial on how to do this on my site www.dnnmine.com . I have some writing to do now, I suppose.

Thanks all

Hi DNN Coder,

Sounds like you have an excellent grasp of where you need to be.  The Linq to SQL layer is designed to replace the traditional data-provider model used historically in modules; the provider model allow for the targeting of multiple persistent stores, but this has not been (largely) realized in practice. 

You are also completely correct -- it is never advisable to link directly to any core framework tables, views, or procedures.  This risks serious issues with future compatibility.

Let me know if you put something together relating to the use of the adapters; I'm always eager to see how my work has been used in production environment!

Brandon