Remember LINQ is actually nothing more than a Querying Language built into the .NET core languages.

Using LINQ to Objects (ie querying over any collection that implements IQueryable or IEnumerable) is trivial in the DNN environemnt - and will have no impact on any other dnn module.

I suspect from comments here that what people are really discussing is "LINQ to SQL" - which is a a combination of the LINQ language together with a data abstraction layer that exposes your Database elements as "IQueryable" objects.  Michael is very passionate about the use of LINQ to SQL and to a degree I support him in this feeling - you do have to be aware of its limitations though.

The major issue is that it is difficult to manage {objectQualifier}s so if you are expecting to distribute a module built with LINQ you will need to be aware of this.

Charles,

You are absolutely right. Definitely you discuss one of the gotchas I've been dealing with.

By the way, in terms of LINQ to SQL, are there any plans to support it in DNN Cambrian with a SQLExceptionHandler to catch any SQL exceptions gracefully and display either friendly messages and/or developer messages without shutting down the DNN page load?

Providing a useful and helpful SQL exception handler well integrated into the database provider for DNN might facilitate better future integration and development of LINQ to SQL based modules for DotNetNuke.

CT