Yeah, it was built back when Microsoft.Windows.Shell was a separate dll, and not incorporated directly into .Net. It's now in the System.Windows.Shell namespace.If you disappear for a long time again, don't forget to upload the source code, because I recently had to decompile your exe with the ILSpy utility.
I wanted to rebuild it, but your app has some third-party stuff in the form of WindowChrome, which had problems during the build.
What I said in that original update was a bit wrong - I hadn't taken a look at my old code at the point I wrote that, so I made some assumptions that turned out wrong.
First off, the parser was written in c# originally - I just forgot what the .dll that I tried to get fancy with, was for. I was correct - at least in spirit with how I handled file loading, though I was at least smart enough to put it in a background loader - I still loaded and collected multiple copies of the same file. The parser also was a lot more accurate than I thought it was - though, due to crashing on some maps, it wasn't especially so.
As far as disappearing goes - I will at least release the version I'm working on. Provided it isn't as much of a buggy mess as what I left you guys with, I'll upload the source.
I honestly thought nobody was interested in it as I left it - considering how many people had issues with getting it working. But if I have someone bumping this thread 6 years later, I must've done something that the existing tools didn't