Outlook Security cannot Trust an add-in created in VB.NET

  • Thread starter Thread starter Norman
  • Start date Start date
N

Norman

I have created an Outlook 2003 add-in using (VS 2003) VB.Net. The
add-in adds a user selected security classification to the body of all
outgoing email messages.

The add-in works perfectly. Now I need to trust this add-in so that
the Outlook security messages do not popup when sending (Exchange
environment).

I realize that I have to create a COM add-in shim to my application.
I have carefully followed the MSDN article "Using the COM Add-in Shim
to Trust 2002 Add-ins Built with VS.Net". My add-in is strongly
named, etc. .etc..

Now, everything works as before, but after trusting the shim dll -
the Outlook security popups are still displayed!!

Any ideas on why this is not functioning? ALSO is there any way to
get feedback as to why a DLL cannot be trusted?
 
Norman said:
I have created an Outlook 2003 add-in using (VS 2003) VB.Net. The
add-in adds a user selected security classification to the body of all
outgoing email messages.

The add-in works perfectly. Now I need to trust this add-in so that
the Outlook security messages do not popup when sending (Exchange
environment).

I realize that I have to create a COM add-in shim to my application.
I have carefully followed the MSDN article "Using the COM Add-in Shim
to Trust 2002 Add-ins Built with VS.Net". My add-in is strongly
named, etc. .etc..

Now, everything works as before, but after trusting the shim dll -
the Outlook security popups are still displayed!!

Any ideas on why this is not functioning? ALSO is there any way to
get feedback as to why a DLL cannot be trusted?
Click to expand...

Addins are usually trusted by default by Outlook 2003, if you go to the
security settings there is a setting to "trust all installed add-ins and
templates". Of course if you can't/don't want to enable that then the
outlook security folder is the only way to go.

The main problem you may be experiencing is that it's the initial
outlook application object you receive thats trusted. Any calls to it to
get objects will return objects that know they are in a trusted
environment. However if you get hold of outlook objects in any other way
then they will not be seen to be trusted. The most common way to do this
is with the objects passed to you in events, they are not trusted and
calls to them and any objects you get from them can throw up the
security dialogs.

Dave
 
Back
Top