Nope. I still get the same
COMException
("name not found") with
app.InvokeMember("Run", BindingFlags.InvokeMethod | BindingFlags.Default, null, Application, new[] { qualifiedMemberName.MemberName });
, ...and the same strategy (invoking the "Run" member) in Excel works perfectly. In fact, I have an
Microsoft.Office.Interop.Excel.Application
instance, that exposes this
Run
member - when the host app is Outlook, I have an
Microsoft.Office.Interop.Outlook
instance, which doesn't expose a
Run
method. It's not just
undocumented... it's simply not there; the mystery remains :-( —
Mat's Mug 1 min ago