Comments by Martijn Boeker

Martijn Boeker 7-Jun-11 15:07pm View

I don't have much hope though :-)
http://social.msdn.microsoft.com/Forums/en-US/windowsdesktopsearchdevelopment/thread/dcfb40ea-b250-4294-80d0-727c7365745e

Martijn Boeker 7-Jun-11 15:04pm View

I reported this as 'not an answer', hoping that this will be an unanswered question again so perhaps someone else will be able to check this out and provide a solution to this problem.

Martijn Boeker 7-Jun-11 14:52pm View

I'm having the same problem. We can use Windows Search to find files and the API appears to have the ability to give a small summary that indicates why the file is a match to the search criteria (System.Search.QueryFocusedSummary). This allows us to render the search results in a similar way that Google does. The real question is, how do we get this value?

To read values through the search SQL syntax, you must select the columns you want to retrieve. I think the comment in the MS document means that System.Search.QueryFocussedSummary is a column that can be used only in the SELECT part of the query, not in the WHERE clause.

If I run a search query, the number of columns returned is the same as the number of columns in the query. There is no extra column as MRB is suggesting.

Martijn Boeker 16-Dec-10 12:27pm View

Deleted

I agree. It will be most useful when you only expect null if something went wrong. For example, you expect Level2 to be not null in 99% of the cases, but you just want to make sure no exception is thrown when it is null. This then leads to the discussion of whether you want to surpress exceptions or not.. So this solution will be useful when you choose to surpress an exception when one of the objects in the path is null, much like the Java syntax enables you to do.

Comments by Martijn Boeker (Top 4 by date)