Outlook Security Manager deployment: Summary
If your application uses the Outlook Security Manager component, you need to know how to deploy it properly. I hope that my series of article will help you on the road. In this final part I will try to sum up all the main points for you to orient yourself better in all this information.
First off, for the Outlook Security Manager component to work, you must have a COM dll registered on a target PC – secman.dll or secman64.dll (or, if you use the ActiveX edition – osmax.ocx, secman.dll or osmax64.ocx, secman64.dll). To know what COM dlls must be necessarily registered in the system for given Outlook versions depending on the technology used in your code, read part 1 of the series: Part 1: Outlook Security Manager 2010 deployment:.net, ActiveX and VCL basics.
Remember – to register those DLLs, in most cases administrative permissions are required, for exceptions please see the note below.
If you want to support both 32-bit and 64-bit versions of Outlook in one setup package of your application, you will need to find out what Outlook version is installed on the target PC and register a COM dll appropriate for the given Outlook version. In Part 2: Outlook Security Manager 2010 deployment: bitness and regsvr32 utility, I described a method of identifying the Outlook bitness, and a way of registering COM dlls by using the regsvr32 utility.
If you deploy your application by using the Visual Studio setup project, you can use the vsdrfCOMSelfReg option of your installer to register the needed COM dll on a target PC. You can find more details on how to do this in Part 3: Outlook Security Manager 2010 deployment: self-registration in a Visual Studio setup project.
If your standalone application (standalone, not an add-in!) was compiled with “Any CPU” compiler option, it will not work in 32-bit Outlook on a 64-bit OS, because “Any CPU” in a 64-bit system will work as a 64-bit application. In order for your application compiled with “Any CPU” to work as a 32-bit application on 64-bit Windows, you need to perform the actions described in Part 4: Outlook Security Manager 2010 deployment: compiling a standalone application with “AnyCPU”.
No administrative permissions are required if you deploy your add-in or standalone application via ClickOnce (see ClickOnce Deployment).
You will learn how to deploy your project with ClickOnce correctly from Part 5: Outlook Security Manager 2010 deployment: Reg Free COM & ClickOnce for Outlook 2010 64-bit.
One Comment
I searched for the article title and discovered this, didn’t think
i’d find my answer