TLViewer

The TLViewer application was designed to be a stand alone Object Browser with a set of extensions that expose the relationship between a TypeLib and Windows Registry, and expand on the Browser Model.

With the standard VBA look, you can quickly see the structure of the Object Hierarchy and Model; you can use the flexible F1 help lookup to view your own CHM files.

By building a Database from a snapshot of the current registry, all pertinent help strings are cached on startup. This allows fast help string lookup, with automatic paging to its library or object. If you want to see what information is gathered from the registry, you can look at the Database in a text editor, or Excel ( as a CSV), or let TLViewer export this info to Internet Explorer.

Internal searching of a TypeLib is not supported. You can fall back on VBA to do this for you.

Early releases were plagued with problems filtering difficult registries. Problems included: control characters in helpstrings, empty subkey collections, broken ProgID->Clsid references. Its easy to introduce this trouble into your registry: simply delete a DLL without unregistering it first.

Any registry errors that are encountered when building our Database are now logged in TLError.log. If we have to filter out a key, the details are written to log.