More in this section
Forums / 3.x Pre-release forums (retired) / Module QueryFilter

Module QueryFilter

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Sean
    Sean avatar
    271 posts
    31 May 2006
    11 Dec 2006
    Link to this post

    Hopefully this isn't to complex to answer in a forum post...

    I have been building a custom module to plug into Sitefinity 3.0, I have been using reflector to look at how you have put together the Blogs module, so far I haven't hit too many stumbling blocks.  There is one thing I haven't been able to figure out so far and that is the FilterQuery classes you are using eg PostQueryFilter, they look to be classes that have been generated by something as they are not human readable.  So my question is, how can I create them without manually having to create the Deserialize routine?

    If this is far too complex to explain in a forum post then don't worry about it too much, I can wait until you release your Job custom module.  But if there is a quick way to point me in the right direction that would be a great help.

    Otherwise creating my own provider has been very good, I think I would have struggled without Reflector though as I have never created a Provider before....  But I think the new way of being able to plug in providers is going to give us a huge amount of flexibility without having to worry about upgrades breaking things...

    Keep up the good work, and I can't wait to see the RC...

    Kind Regards
  2. Bob
    Bob avatar
    330 posts
    30 Dec 2016
    11 Dec 2006
    Link to this post
    Hello Sean,

    Actually it is not necessarily to implement QueryFilter class at all. The idea of this class is to allow persistence of search parameters for later use.

    This functionality is not fully implemented yet and QueryFilter classes are subject to change. The only thing they do right now is to pass parameters from the UI to the underlying provider which of course can be implemented as method parameters.

    Kind regards,
    the telerik team
2 posts, 0 answered