|Number of votes:||5|
I have a large list of things within the .Net world in which I would like to enrich my knowledge with. For a while now custom Linq query providers and expression trees have been one of the things I wanted to learn more about.
For the last few days during my daily commute I have been knocking together a query provider which will sit on top of FindPagesWithCriteria API.
Why would I want to do this you may ask? Well, just because I can and it also enriches my knowledge
Last year Johan Olofsson blogged about Linq to PageData, I personally have not got round to playing with this but it does look very useful.
FindPagesWithCriteriaContext is no replacement for what Johan has previously done but I personally think if you do use FindPagesWithCriteria in your everyday job, it’s a nice little wrapper on top of the FindPagesWithCriteria API.
The code has been tested at a very rudimentary level, but there could well be issues. Also, QueryBuilder’s and expression trees are new to me and although the code works I possibly could have gone about things in a better way and possibly areas of code could be optimized. But, hey this was a learning exercise with possibly something slightly useful coming out of it. Well, I think so anyway
Download the FindPagesWithCriteriaContext.cs class from here and add it to your project file.
The code has a dependency on PageTypeBuilder. This is because some classes within PTB are used to resolve PageTypeID’s and property data types.
There are two classes that can be used for the Linq based FindPagesWithCriteria queries these are FindPagesWithCriteriaContext and FindAllPagesWithCritieraContext.
These classes have constructors that accept the usual FindPagesWithCriteria method call parameters.
The following operators are supported in the Linq syntax:
The query provider only has support for where and order by clauses.
An example Linq query is below:
When the Linq query is created the relevant PropertyCriteria the Linq query is converted to will be written to the output window in debug mode.
The criteria for the query above looks like the following:
When the query is then executed, depending on whether you are using the FindPagesWithCriteriaContext or the FindAllPagesWithCriteriaContext classes will determine whether access rights and permissions are ignored or not when retrieving PageData objects.
When creating an instance of the Context classes above you can specify a TypeParam which must inherit or be of type PageData. If you provide a PageTypeBuilder class then the pages returned from the query call will be converted to the PageTypeBuilder type.
When building up the Linq query, inline values, variables and method calls can be used for the property values being compared to.
I better protected myself just in case anybody wants to give it a go and use it .
I have done some rudimentary testing on the query provider and it seems to be working as I would like but there could well be bugs that I have not found .
So, in short use at your own risk and I would recommend when creating your own queries you should verify the PropertyCriteria the query has been translated to in the Output window.
Feedback as always is greatly received. If there are bugs/issues please feel free to email or twitter me @croweman and I will do my best to resolve them. Thanks for reading