vb.net and sending email with outlook

Hopefully Caspar Boekhoudt or someone else, has a second to answer my question. I tried the code and interesting enough the c# path worked, however the vb.net path (could not compile) gave the following error on newMail.send() Send is ambiguous across inherited interfaces 'Outlook._MailItem' and 'Outlook.ItemEvents_Event I was hoping to break the ambiguity by dimensioning something down the "namespace tree" some how change the send to something like mysend dim mysend as Outlook.MailItem = new MailItem newMail.myssend BUT IT DIDN'T WORK

It took a bit of searching on the Microsoft.com site but I found (when I searched for how to report a bug - nothing else I tried came close): http://support.microsoft.com/default.aspx?scid=kb;en-us;315981 which is article 315981 BUG: Visual Basic .NET "'[Method]' is ambiguous across the inherited interfaces" Error Message When Using Office Automation _______________________________________________________ so I was close the way to break the ambiguity on my case was to change newMail.send() to CType(newMail, Outlook._MailItem).Send() _______________________________________________________ or in their words: CAUSE When you import a COM reference into your .NET project, Visual Basic .NET automatically generates a runtime callable wrapper (RCW) to wrap the component and expose it to the Common Language Runtime as a native .NET object. This object implements the default interface for the COM object, and exposes functionality for sinking the default events. If the object that is wrapped has both a method and an event with the same name, the default RCW sets up conflicting names, and Visual Basic .NET is unsure which interface member your code is attempting to access. RESOLUTION To resolve this problem, you can use one of the following methods: Explicitly cast the object to the correct interface before you call the Quit method. For example, you can use the following: CType(oWordApp, Word._Application).Quit() -or- Change the variable declaration to use the extended Class wrapper object for the object. For example, instead of using Word.Application, change the declaration to resemble the following: Dim oWordApp As New Word.ApplicationClass() So now Thanks to Casper, I can automatically email all my recruiters and ask them to please find me a job.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Administrator24y ago
It took a bit of searching on the Microsoft.com site but I found (when I searched for how to report a bug - nothing else I tried came close): http://support.microsoft.com/default.aspx?scid=kb;en-us;315981 which is article 315981 BUG: Visual Basic .NET "'[Method]' is ambiguous across the inherited interfaces" Error Message When Using Office Automation _______________________________________________________ so I was close the way to break the ambiguity on my case was to change newMail.send() to CType(newMail, Outlook._MailItem).Send() _______________________________________________________ or in their words: CAUSE When you import a COM reference into your .NET project, Visual Basic .NET automatically generates a runtime callable wrapper (RCW) to wrap the component and expose it to the Common Language Runtime as a native .NET object. This object implements the default interface for the COM object, and exposes functionality for sinking the default events. If the object that is wrapped has both a method and an event with the same name, the default RCW sets up conflicting names, and Visual Basic .NET is unsure which interface member your code is attempting to access. RESOLUTION To resolve this problem, you can use one of the following methods: Explicitly cast the object to the correct interface before you call the Quit method. For example, you can use the following: CType(oWordApp, Word._Application).Quit() -or- Change the variable declaration to use the extended Class wrapper object for the object. For example, instead of using Word.Application, change the declaration to resemble the following: Dim oWordApp As New Word.ApplicationClass() So now Thanks to Casper, I can automatically email all my recruiters and ask them to please find me a job.
+1