The other day I was trying to extract bookmarks from my IE's history cache, but could not find any tools in IE to do that. Looked around on Google and found a VB Project, which is fine, but I am looking for something using C#. Then, I found this article on CodeProject titled The tiny wrapper class for URL history interface in C#, which would work, but I want a simple script that I can tweak and just run from the command prompt. Again, it would be nice if it is in C# as I have been using this C# Script tool for a while and I really love it. It is called The C# Script Engine by Oleg Shilo and I would highly recommend you explore it if you are not already aware of this gem. It is really clean and lean and does not require any special syntax or setup and could simply use a file that was created with Visual Studio. If you want to automate something and want to do it in C#, this is the tool to use. I would have more to write about this tool later.
Back to our original task, searching on the API calls that are referenced in the above articles, I found the following two links (one on MSDN and one on Google's Code project) which looked promising:
HOW TO: Clear the Cache When Your Application Hosts a WebBrowser Control in Visual C# .NET
WinApis.cs file on Google Code project called csexwb2 - The most complete .NET Webbrowser control wrapper
Mostly based on the code given in WinApis.cs, I written a C# Script that can be run using the C# Script Engine mentioned above or can also be run using csc.exe that comes with the .NET Framework. You could also add this to any C# IDE Project file and run it from there. It writes the entries from IE's cache to a text file called "ieHistory.txt".
The code in the above script file is pretty self explanatory, but I would like to mention a few things that might come handy if you like to experiment with or tweak the script more.
On the MSDN page, it declares the lpszSourceUrlName and lpszLocalFileName as IntPtr and I had problem converting these fields to Strings, so I used the struct definition given in csexwb2.
Using the PInvoke declarations on MSDN page, I was not able to get it recognize the urlPattern argument, and I had to use the declarations given in csexwb2.
Hope you find this useful.
Best Wishes,
Sonny