Extensibility Model for Add-Ins

[omar]

This is my first post on Linqer and I will start by saying that Linqer is a great productivity tool that made writing Linq queries so much more pleasant.

In our development we are using LLBL as our ORM platform and LLBL has first class LINQ support with its own LinqToLLBL.

While LLBL's LINQ is very similar to that of LinqToSQL I was hoping for a way for Linqer to add first-class support to other querying sources like LLBL.

LinqPad are doing this with a new enhancement called "LINQPad Data Context Extensibility Model" that would offer first-class support for other databases and querying sources. This extensibility model lets us write plug-ins that displays our own 'Add Connection' dialog and then shows custom objects in the Schema Explorer.

Any plans for the same with Linqer?

[Mikhail Oumantsev]

Internal Linqer structure allows writing such plug-ins.
I have a product Linqer.dll, which has a common Linqer provider implementation. A new class inherited from this common provider can implement a custom model support.
Currently there are two providers implemented in Linqer, they are LINQ to SQL and LINQ to Entities providers.
The only thing is both providers support MSSQL SQL dialect.
A SQL dialect cannot be part of such provider, it has to be part of the Linqer engine, because of the engine complexity.