Security Manager
for Microsoft® Outlook®Add-in Express Home > Outlook Security Manager > Online Guide > Deployment 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, depending on the Outlook version installed on the target PC, register one of them as a COM object. You need to register secman64.dll for Outlook 2010 64-bit only. You can find the Outlook 2010 bitness by checking the Bitness value in the registry key below; if the value is "x64", register secman64.dll, otherwise, register secman.dll. The registry key to check is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook
To register, you can use the regsvr32 utility or special options of your installer (vsdrfCOMSelfReg for example). In addition, your setup package must include SecurityManager.dll (SecurityManager.2005.dll) that must be located in the application install folder. Note that administrative permissions are required to register secman.dll or secman64.dll.
Note that for a standalone application (not an Outlook add-in!), the bitness of the application must be the same as that of Outlook, not the bitness of the operating system. That is, your application must be 32-bit if used for Outlook 2000-2007 and Outlook 2010 32-bit; it must be 64-bit if used for Outlook 2010 64-bit. In terms of Visual Studio, you must never use AnyCPU as the platform for which you build your application; the platform must be x86 for Outlook 2000-2007 and Outlook 2010 32-bit and x64 for Outlook 2010 64-bit. You set a correct platform in the Configuration Manager dialog, see menu Build | Configuration Manager.
Pay attention, please, that you should place secman.dll (secman64.dll) as a shared DLL into the shared folder of Windows, Common Files \ Outlook Security Manager. Do not unregister secman.dll (secman64.dll) if it existed before installing your product. You can find the complete information about deploying shared files on the MSDN website: Windows 2000 Application Specifications: Component Sharing
Note.You can find the redistributable version of secman.dll and secman64.dll in the Redistributable subfolder of the Outlook Security Manager folder.
Per-user Registration
Note that you can deploy your .NET solution that uses the Security Manager using ClickOnce. You don't need to do anything special; just deploy your solution. There's a problem however: if two solutions install the Security Manager in this way, then uninstalling one of them will break the other one. To bypass this problem use RegFree COM which is available for Windows XP and higher. Please have a look at the following samples on our blog:
HowTo: Deploy Outlook Security Manager with ClickOnce using Reg Free COM
HowTo: Deploy Outlook Security Manager with ClickOnce using Reg Free COM, part 2
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.
VCL edition
To deploy your software that uses Outlook Security Manager you should include the secman.dll file to your setup package and register it on an end-user computer as a COM object. To register it you can use the regsvr32 utility or special options of your installer. Please pay attention that you should place secman.dll as a shared DLL into the shared folder of Windows, Common Files \ Outlook Security Manager. Please do not unregister secman.dll if it existed before you install your product.
You can find the redistributable version of secman.dll in the Redistributable subfolder of Outlook Security Manager folder.
ActiveX edition
To deploy your software that uses Outlook Security Manager, include the secman.dll and osmax.ocx as well as secman64.dll and osmax64.ocx files into your setup package and, depending on the Outlook version installed on the target PC, register one of the pairs as COM objects. You need to register osmax64.ocx and secman64.dll for Outlook 2010 64-bit only. You can find the Outlook 2010 bitness by checking the Bitness value in the registry key below; if the value is "x64", register secman64.dll and osmax64.ocx, otherwise, register secman.dll and osmax.ocx. The registry key to check is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook
To register, you can use the regsvr32 utility or special options of your installer.
Note that for a standalone application (not an Outlook add-in!), the bitness of the application must be the same as that of Outlook, not the bitness of the operating system. That is, your application must be 32-bit if used for Outlook 2000-2007 and Outlook 2010 32-bit; it must be 64-bit if used for Outlook 2010 64-bit.
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. You can find the complete information about deploying shared files on the MSDN website: Windows 2000 Application Specifications: Component Sharing
Note.You can find the redistributable version of secman.dll, secman64.dll, osmax.ocx and osmax64.ocx in the Redistributable subfolder of the Outlook Security Manager folder.
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" and "a program is trying to automatically send email". See also a flash video showing how to disable a message like: "A program is trying to access your Address Book or Contacts".
Back to Outlook Security Manager homepage | 
