Why use "DLLSelfRegister" in VB deployment package?

Question

Why would you use DLLSelfRegister in a VB deployment package?

I am trying to sort out possible conflict problems with a calendar control: msacal70.ocx. Apparently there is a conflict with newer Office calendar controls. This might be the cause of Automation Error showing after the package is deployed to some machines.

I noticed the setup.lst for the VB deployment package uses DLLSelfRegister for this control. What are the effects of allowing a DLL to self-register and would removing DLLSelfRegister cause the ocx to register during installation of the package?

Answer 1

DLLSelfRegister simply tells the installer that the DLL is in fact a COM component that can be registered. Without this the DLL would not get registered and thus would not be properly usable. Registering writes information about the component to the register that clients use to create instances of the component. Here is more information about the Package and Deployment Wizard.