> Can of worms indeed! I'd prefer the `IHostApplication` approach, much fewer moving parts... besides if we only implement Excel, Word, and Access, we'll already cover 99% of the needs. A `FileSystemWatcher` would be something we would use, say, to detect changes to code files made outside the editor (and prompt to reload/replace the code file), say, in VB6 (or, in VBA, in a source control / repository scenario).
Plus `hostApp.ActiveDocument.Name` might be a COM hit, but it shouldn't involve