用WiX注册COM服务器 [英] Registering a COM server with WiX

问题描述

我一直在尝试确定使用WiX注册COM服务器来创建Windows Installer程序包的最佳案例解决方案，并且正在努力工作.

I have been trying to determine a best case solution for registering a COM server using WiX to create a Windows Installer package and am struggling.

在此帖子中部署工程存档:HOWTO:将Regsvr32.exe与WIX一起使用，对于安装警察"有一个公开的要求，以通过exe自定义操作严厉打击使用regsvr32.我知道使用regsvr32的弊端，因为它注册到系统而不是用户，但我还记得OleSelfRegister可能会遇到Microsoft支持公告中的问题(对不起，找不到链接)-我相信他们建议使用regsvr32.

In this post Deployment Engineering Archive: HOWTO: Use Regsvr32.exe with WIX, there is an open request for the "Setup police" to crack down on using regsvr32 through an exe custom action. I know the evils of using regsvr32 as it registers to the system rather than the user, but I also recall that OleSelfRegister can have issues from a microsoft support bulletin (sorry, can't find the link) - and I believe they recommended using regsvr32.

有什么建议吗?

推荐答案

在以下位置阅读不要使用SelfReg和TypeLib表":

Read "Do not use the SelfReg and TypeLib tables" at:

https://msdn.microsoft.com/en-us/library /bb204770#no_selfreg

对于WiX，请查看以下架构参考中的 Component 元素:

For WiX, take a look at the Component element in the schema reference at:

http://wixtoolset.org/documentation/manual/v3 /xsd/wix/component.html

注意某些子元素，例如 AppId ， Class ， ProgId ， Registry 等.正确的技术是使用COM extraction反映注册信息并将其声明性地发送到您的安装程序中，以便MSI可以为您处理它，而不会处理某些可能失败且也不会失败的代码(例如DllRegisterServer())从维修和广告的角度提供MSI对组件占用空间的洞察力.

Take notice of certain child elements such as AppId, Class, ProgId, Registry and so on. The proper technique is to use COM extraction to reflect the registration information and emit it declaratively into your installer so MSI can take care of it for you without going out of process to some code (like DllRegisterServer()) that could fail and also not provides MSI insight into the footprint of the component from a repair and advertisement perspective.

这篇关于用WiX注册COM服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！