具有共享子安装程序的安装程序？
我们构建了一堆具有相似结构的产品，实际上共享已安装的子目录、文档和各种系统配置变量（环境变量、开始菜单项……）
我们一直在使用InstallShield。它可以工作，但是每次单击鼠标来配置产品安装程序是非常痛苦的，特别是当其他安装程序已经具有 90% 相同的配置时。
作为程序员，我们习惯于使用子例程来完成常见的工作。为什么这个想法不适用于安装人员？
是否有一种简单的方法来配置已安装功能的子集并在一组 InstallShield 安装程序中使用它们？
作为替代方案，我们一直在考虑使用 NSIS，因为即使我们必须实现宏扩展逻辑，共享逻辑也可以分解为子例程（？）或宏。有人在这里有经验或建议吗？与InstallShield相比，NSIS作为安装程序有什么能力缺陷吗？
We build a bunch of products that all have a similar structure, and in fact share installed subdirectories, documentation and various system configuration variables (environment variables, start menu items, ...)
We've been using InstallShield. It works, but it is incredibly painful to configure a product installer one mouse click at a time, especially when the other installers already have 90% the same configuration.
As programmers, we're used to subroutines to do common work. Why shouldn't this idea apply to installers?
Is there an easy way to configure a subset of installed features and use them across a set of InstallShield installers?
As an alternative, we've been considering using NSIS on the grounds that the shared logic can be broken out as a subroutine(?) or a macro even if we have to implement the macro expansion logic. Does anybody have an experience or recommendations here? Does NSIS have any capability shortcomings as an installer compared to InstallShield?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
尝试制作合并模块，它们就像编程中的子程序，只需一键点击即可轻松添加到您的 VS Installer 项目中。
Try making merge modules, they are like subroutines in programming, and they can be easily added into your VS Installer projects with just one click.