Wish List

Sep 24, 2008 at 10:02 PM
  1. Figure out a way to avoid the dependency on Microsoft.SharePoint.dll. This would entail finding another way to enumerate the documents from the site. It's possible that the SharePoint SQL database could be queried directly for this information.
  2. Figure out a way to avoid the dependency on the Office run-time. Is there an OLE interface built into Windows that could be used instead? We wouldn't be able to open the documents then, but perhaps we could just extract the text programmatically that way.
  3. Figure out a way to enumerate indexed terms directly from SharePoint. Then run the RegEx matcher against those. This would entail learning where the indexer stores those terms (presumably in the MSDE instance that belongs to WSS) and how. This would not only solve the above issue, but also greatly improve the performance of the tool.
  4. Provide a simple GUI interface.
Oct 7, 2008 at 7:35 PM
It would also be nice to give the command the root path of a site and have it find and scan all libraries contained within.  Handy rather than iterating over them in a script.
Oct 17, 2008 at 5:57 PM
Hmm, that's a good idea. Looking into it ...
Oct 20, 2008 at 5:26 PM
Regarding iterating over all of the libraries in a specified site, we just re-tested the latest posted version of the tool and it already does this. Did it not work for you?

C:\test\sharepoint>SharepointSearch.exe http://localhost:43798 \d{3}-\d{2}-\d{4}
Search office documents on site http://localhost:43798 for \d{3}-\d{2}-\d{4}:
333-22-4444),http://localhost:43798/Design/All of the existing.docx,0
Note: Design is a document library. Requirement is another document library.
Sep 10, 2012 at 2:51 PM


Do you know what specific DLL's contain the functions you were require from Microsoft Office?  I am wondering if some simple include statements with some, "copied" dll's from both SharePoint and Office will fix the Office/SharePoint server dependencies.

Sep 10, 2012 at 3:06 PM

Yes, regarding SP, it's Microsoft.SharePoint.dll. See this thread: http://mossregexsearch.codeplex.com/discussions/36417.

Regarding Office, I don't remember specifically, but that seems like less of an issue since there's no manual step required for resolving the MSO references.