The customizable overload of QueryFactory.CreateLinqQuery now takes an instance of IQueryParser instead of MethodCallExpressionNodeTypeRegistry. This has been caused by refactorings made in the course of the addition of new features, and it is easily remedied.
To create a default query parser:
To create a customized query parser:
(Note that QueryParser does not change state between different queries, so it can be stored and reused with "singleton" semantics. It is of course possible to use a dependency injection container rather than manually composing the parser.)