Hi all!
What I've been reading about using LINQ2SQL for the DAL never considered the databaseOwner and objectQualifier placeholders. In case of the Linq2Sql entity designer, the generated code will only work with the exact same settings used, when creating the entity model. If you want to use this DAL on an installation that has different settings, the tables (and also stored procedures) will surely not be found, since they have different names.
Furthermore, I have not yet been able to find an easy way to dynamically name tables/functions in a linq entity model. So far, I have come up with the solution of providing my own custom MappingSource, using the AttributedMappingSource internally for the basic mapping, and adding custom code for the mapping. The downside is, that you need not only create the custom MappingSource, but also the matching MetaModel and MetaTable classes, as the tables' names are stored that far down in the MappingSource.
I'm currently playing around with it a bit, and maybe there will be a way to implement this using generics. But I would currently not consider LINQ2SQL an alternative for the regular DNN DAL, unless you like living dangerously.
Best regards
Christoph