Deployment of applications
Outlook Security Manager Developer's Guide

Security Manager
for Microsoft® Outlook®

Add-in Express Home > Outlook Security Manager > Online Guide > Deployment

Deployment

• .NET edition - deployment
• Delphi VCL edition - deployment
• ActiveX edition - deployment

.NET edition

To deploy your software that uses Outlook Security Manager, include the secman.dll and secman64.dll files into your setup package and deploy them in one of these ways:

• Register both secman.dll and secman64.dll as COM servers; this requires administrative privileges. Note that you only have to register secman64.dll on a 64bit PC. This approach allows specifying a profile-independent location for the files. Pay attention, please, that you should place secman.dll and secman64.dll as shared DLLs into the shared folder of Windows, Common Files \ Outlook Security Manager. Do not unregister secman.dll and secman64.dll if they exist in that folder when you install your product.

• Put secman.dll and secman64.dll into the folder where all files of your application are located. This approach doesn't require registering the files.

Note that the deployment options above allow any combination of bitnesses of your application and Outlook. Still, with a 32bit Outlook on a 64bit PC this works only if Security Manager is able to find secman.dll and secman64.dll; this requires that you put both files in the same folder or register them. A particular advantage of using both secman.dll and secman64.dll files is: your application will work even if the end user installs Outlook (Office) of a different bitness.

Attention!

You should understand that Outlook Security Manager may potentially open a door for unsafe content. To avoid this you must enable Outlook security in a finalization code after each elementary call of the protected objects as shown in the examples above.

For detailed step-by-step instructions, please see the 5 part tutorial on our blog: Outlook Security Manager deployment.

VCL edition

To deploy your software that uses Outlook Security Manager, include the secman.dll and secman64.dll files into your setup package and deploy them in one of these ways:

• Register both secman.dll and secman64.dll as COM servers; this requires administrative privileges. Note that you only have to register secman64.dll on a 64bit PC. This approach allows specifying a profile-independent location for the files. Pay attention, please, that you should place secman.dll and secman64.dll as shared DLLs into the shared folder of Windows, Common Files \ Outlook Security Manager. Do not unregister secman.dll and secman64.dll if they exist in that folder when you install your product.

• Put secman.dll and secman64.dll into the folder where all files of your application are located. This approach doesn't require registering the files.

Note that the deployment options above allow any combination of bitnesses of your application and Outlook. Still, with a 32bit Outlook on a 64bit PC this works only if Security Manager is able to find secman.dll and secman64.dll; this requires that you put both files in the same folder or register them. A particular advantage of using both secman.dll and secman64.dll files is: your application will work even if the end user installs Outlook (Office) of a different bitness.

ActiveX edition

To deploy your software that uses Outlook Security Manager, add secman.dll and osmax.ocx as well as secman64.dll and osmax64.ocx to your setup package. You need to register them as follows:

• On a 32bit Windows, you register secman.dll and osmax.ocx

• On a 64bit Windows, you register secman.dll and secman64.dll. Also, you register osmax.ocx if your application is 32bit; register osmax64.ocx if your application is 64bit.

To register, you can use the regsvr32 utility or special options of your installer; administrative privileges are required.

Note that the deployment rules above allow any combination of bitnesses of your application and Outlook. Still, with a 32bit Outlook on a 64bit PC this works only if both secman.dll and secman64.dll files are registered. A particular advantage of using both secman.dll and secman64.dll files is: your application will work even if the end user installs Outlook (Office) of a different bitness.

Please pay attention that you should place secman.dll, secman64.dll, osmax.ocx, and osmax64.ocx as shared DLLs into the shared folder of Windows, Common Files \ Outlook Security Manager. Please do not unregister them if they existed before installing your product.

Attention!

You should understand that Outlook Security Manager may potentially open a door for unsafe content. To avoid this you must enable Outlook security within a finalization code after each elementary call of the protected objects as we showed in the examples of how to disable warnings like: "A program is trying to access email addresses". See also a flash video showing how to disable a message like: "A program is trying to access your Address Book or Contacts".