Why use "DLLSelfRegister" in VB deployment package?
- by Craig Johnston
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.
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?