如何将Setup.exe、Setup.msi 和.NetFramework 必备组件合并到单个安装程序中?
如何将 vs2010 安装项目中的安装文件和必备文件合并在一起? ..在我的发布目录中有 3 个文件:
setup.exe
Setup1.msi
DotNetFX40Client/dotNetFx40_Client_x86_x64.exe
并且我需要将这些文件放在一个简单的安装文件中。
我尝试使用 Windows 中的 IExpress 工具,但它不起作用,因为“dotNetFx40_Client_x86_x64.exe”位于目录内,并且该工具不支持它。
有什么方法可以让 setup.exe 在根文件夹中查找 .net Framework 先决条件 所以我可以使用 IExpress 工具?如果没有,还有其他方法可以将这些文件合并到一个安装程序中吗?
提前致谢!! 干杯!
How can the setup files and prerequisite files from a vs2010 setup project be merged together?
..in my release directory there are 3 files:
setup.exe
Setup1.msi
DotNetFX40Client/dotNetFx40_Client_x86_x64.exe
and I need these files to be in one simple setup file.
I tried using IExpress tool from windows but it doesn't work because "dotNetFx40_Client_x86_x64.exe" is inside a directory, and the tool does not support it.
Is there any way to make setup.exe look for the .net framework prerequisite in the root folder
so I can use the IExpress tool??And if not, is there any other way to merge these files into a single installer?
Thanks in advance!!
Cheers!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
使用 NSIS 安装程序 - 您可以在此处找到它,此处。以下是适用于您的使用场景的语法示例:
然后,NSI 文件被编译为单个文件安装程序,其中将所有材料包含在一个 exe 中 - 该 exe 文件的功能可以是简单解包和执行您自己的安装之间的任何位置.exe 文件和完整的自定义安装程序(不明白为什么您会在您的情况下需要它)。
Make use of the NSIS installer - you may find it here, there's tutorials to be a plenty from here. Here's an example of the syntax adopted to your usage scenario:
The NSI file is then compiled into a single file installer that includes all your material in one exe - the functionality of that exe file can be anywhere in between simply unpackaging and executing your own setup.exe file and a full custom installer (can't see why you would want that in your case).
我使用 dotNetInstaller 1.10 作为构建后步骤(原始安装程序,[可选] MSI,并且任何支持包都包含在 dotNetInstaller 输出可执行文件中):
需要做一些工作才能让“规则正确”,但对我来说已经足够了。
快乐编码。
I have had a good bit of success using dotNetInstaller 1.10 as a post-build step (the original installer, [optional] MSI, and any support bundles are wrapped into the dotNetInstaller output executable):
It takes some work to get the "rules correct", but it Works Well Enough for Me.
Happy coding.