嵌套部署 [英] Nested deployment

查看:79
本文介绍了嵌套部署的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我不知道我是否可以做这样的事情:

I do not know if I can do something like this:

Setup1.msi-将一些文件安装到文件夹A中,并在注册表中添加一个密钥以指示Setup1安装成功.

Setup1.msi - install some files to folder A and add a key in registry to indicate the success of Setup1 installation.

Setup2.msi-其他一些文件和Setup1.msi.在安装开始时,请通过检查注册表来检查是否已成功安装Setup1.如果没有,请运行Setup1.msi.然后,将其文件正常安装到文件夹B.

Setup2.msi - some other files and Setup1.msi.  At the beginning of installation, check if Setup1 has been installed successfully by checking registry.  If not, run Setup1.msi.  Then, go for normal installation of its files to folder B.

如果可以完成,该如何在Setup2 msi项目中完成呢?

If it can be done, how do I do it in Setup2 msi project?

我不想将Setup1文件明确包含到Setup2中,因为我将拥有Setup3,Setup4等.它们都将需要Setup1文件作为基本模块.此外,Setup1文件将被放置在一个文件夹中,而其他设置将被放置 在不同的文件夹中.

I do not want to include Setup1 files into Setup2 explicitly because I will have Setup3, Setup4,.. SetupN.  All of them will need Setup1 files as base module.  Moreover, Setup1 files will be placed in one folder while the other setups will be placed in different folders.

谢谢.

 

推荐答案

您无法进行递归MSI安装,因为它们一次只能安装一次,所以您可以如果您正在考虑的话,请运行setup2的自定义操作setup1.

You can't do recursive MSI installs, they're one at a time, so you can't run setup2 deom a custom action of setup1, if that's what you were thinking.

这类事情通常是通过一个程序将它们一个接一个地安装来完成的.如果setup1是一组通用组件,则将它们构建为合并模块,并将其包括在其他设置中.这样可以避免用户中断一切 卸载setup1.

This type of thing is often done with a program that installs them one after the other.  If setup1 is a set of common components, then build them as a merge module and include them in the other setups.  This avoids everything breaking if the user uninstalls setup1.

如果要将setup1作为先决条件,请查看Bootstrap Manifest生成器.

If you want to treat setup1 as a prerequisite, look at the Bootstrap Manifest generator.


这篇关于嵌套部署的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆