SecurityManager.ConnectTo is launching Outlook window

Add-in Express™ Support Service
That's what is more important than anything else

SecurityManager.ConnectTo is launching Outlook window
 
charliehomo




Posts: 15
Joined: 2012-11-15
Hi Andrei,

Looks like the culprit, on my machine at least, is the WebEx Productivity Tools Outlook add-in:

HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\WebExOI.Addin

If I set LoadBeh * avior=0, then the Outlook Window doesn't appear.

What do you think?

Charlie
Posted 19 Nov, 2012 09:27:25 Top
Andrei Smolin


Add-in Express team


Posts: 14115
Joined: 2006-05-11
Hi Charlie,

It's good that you've found this add-in. Bad that you have it. Make sure that it is disabled when you run your program. I suppose there may be other add-ins showing the same behavior. Alas.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 19 Nov, 2012 10:25:22 Top
charliehomo




Posts: 15
Joined: 2012-11-15
Hi Andrei,

Yes. Is there anything that can be done on your side to prevent this from happening?

Charlie
Posted 19 Nov, 2012 10:26:58 Top
Andrei Smolin


Add-in Express team


Posts: 14115
Joined: 2006-05-11
Hi Charlie,

There's no way, unfortunately: no our code is run when you issue this call.

The add-in uses the Outlook object model in a perfectly legal way, it simply doesn't comply with unwritten rules of user-friendly behavior.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 19 Nov, 2012 10:44:54 Top
charliehomo




Posts: 15
Joined: 2012-11-15
Hi Andrei,

Got it. Is there a way for me to prove this to the WebEx people? Do you have simple vba/vb6 code I can demonstrate this problem to them with? What happens behind the scenes when SecurityManager.ConnectTo runs?

Any help would be great in case they blame this on us :)...

Charlie
Posted 19 Nov, 2012 10:56:24 Top
Andrei Smolin


Add-in Express team


Posts: 14115
Joined: 2006-05-11
Oh, now I understand your question. The Security Manager gets an Outlook.Explorer exactly in the way shown in that sample project:

Set IOutlookExpl = IOutlook.GetNamespace("MAPI").GetDefaultFolder(6).GetExplorer

6 above stands for Outlook.OlDefaultFolders.olFolderInbox.

And after further discussion with our developers, we've found a workaround for you. Instead of supplying an Outlook.Application object to the ConnectTo method, do the following:

- create a new Outlook item (e.g. a MailItem) via m_oOutApp.CreateItem(...)
- get the inspector object for that item via MailItem.GetInspector
- pass that inspector to the ConnectTo method.

Please let me know if this works for you.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 19 Nov, 2012 11:08:41 Top
charliehomo




Posts: 15
Joined: 2012-11-15
Hi Andrei,

Great, thank you! I will let you know if this doesn't work for me.

Charlie
Posted 19 Nov, 2012 11:13:32 Top
charliehomo




Posts: 15
Joined: 2012-11-15
Hello Andrei,

So, supplying the 'inspector' object instead of the Application object works much better, thank you.

The only problem I have now is with the Outlook instance in the system tray, which doesn't go away once I end my program. It did disappear when I was connecting to the Outlook instance. Do you have any idea how to fix this?

Charlie
Posted 25 Nov, 2012 20:01:17 Top
Andrei Smolin


Add-in Express team


Posts: 14115
Joined: 2006-05-11
Charlie,

Does the same occur if you turn all other CPM add-ins off? If yes, please send me the current version of your code to the support email address, see {Add-in Express}\readme.txt. I won't need the whole code, I'll need to look at how you use Outlook objects.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 26 Nov, 2012 01:35:20 Top
charliehomo




Posts: 15
Joined: 2012-11-15
Hello Andrei,

I just sent the code to the Support email. Turning off all other add-ins didn't make a difference.

Regards,

Charlie
San Francisco
Posted 26 Nov, 2012 12:52:52 Top