为什么使用“DLLSelfRegister”在VB部署包中？
为什么要在 VB 部署包中使用DLLSelfRegister？
我正在尝试解决与日历控件可能存在的冲突问题：msacal70.ocx。显然与较新的 Office 日历控件存在冲突。这可能是包部署到某些计算机后显示自动化错误的原因。
我注意到 VB 部署包的 setup.lst 使用 DLLSelfRegister 来控制此控件。允许 DLL 自注册以及删除 DLLSelfRegister 会导致 ocx 在软件包安装过程中注册会产生什么影响？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
DLLSelfRegister只是告诉安装程序该 DLL 实际上是一个可以注册的 COM 组件。如果没有这个，DLL 将不会被注册，因此将无法正确使用。注册将有关组件的信息写入客户端用来创建组件实例的寄存器。以下是有关打包和部署向导的详细信息。DLLSelfRegistersimply 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.