by matt
5. October 2006 18:36
Sheesh. After finally detailing how I setup a blank ATL COM project, I thought I might as well actually begin to develop something. Of course I'd forgotten something. We've already seen what a mess the documentation is in, but what about SDKs?
Firstly, we're going to need the Windows Desktop Search API SDK. This is a nice little zip file that includes a couple of idl files. There's a wdsQuery.idl that gives a coclass and an interface for issuing queries, a wdsView.idl that appears to allow you to host the WDS results viewer (with previewer?). The one we're interested in, though, is wdsSetup.idl, that gives a few interfaces to aid in registering a protocol handler. It even includes the CLSID of the object that implements ISearchManager that I was worrying about last time.
But it doesn't include the ISearchProtocol interface itself.
Looking at the Other Resources section of the MSN Search Toolbar guide (isn't it called Windows Desktop Search these days, guys?) there's a link to some documentation on protocol handlers (as I pointed out last time), and there's a link to a knowledge base article that includes a link to download the 2001 SharePoint Portal SDK, which includes the definition of ISearchProtocol. We're going to use this.
It's probably worth getting the latest Platform SDK, too. You could go cutting edge and get the latest beta of the Windows SDK - but bear in mind that it includes the beta bits of the .net 3 framework...
Of course, since the whole point of this protocol handler is to search IE7's RSS feed store, you'll need headers for that too. They are included in the Windows SDK, or you can get them on the cheap from the RSS team blog.
Right. I think we're set. But I've said that before.
Subscribe