InstallShield的"Full"可再发行的力量迫使互联网接入 [英] InstallShield "Full" Redistributable forces internet access

查看:97
本文介绍了InstallShield的"Full"可再发行的力量迫使互联网接入的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用Flexera的InstallShield Express将软件捆绑到Setup.exe文件中.我包括了可重新分发的.NET Framework 4.7.1(2.指定应用程序数据>"Microsoft .NET Framework 4.7.1 Full"已选中并在中间面板中突出显示,并说本地安装">在功能选择之前安装"已选中底部面板).

I used Flexera's InstallShield Express to bundle my software into a Setup.exe file. I included .NET Framework 4.7.1 redistributable (2. Specify Application Data > 'Microsoft .NET Framework 4.7.1 Full' is checked and highlighted in middle panel, and says 'installed locally' > 'Install before feature selection' is checked on bottom panel).

我进入没有Internet访问的全新安装的Windows 7计算机,并尝试安装.它给了我错误:

I went onto my fresh installed Windows 7 computer with no internet access and attempted the install. It gave me the error:

"下载文件时发生错误 http://saturn.installshield.com/is/prerequisites/Microsoft.NET Framework 4.7.1 Full.prq"

"An error occurred while downloading the file http://saturn.installshield.com/is/prerequisites/Microsoft.NET Framework 4.7.1 Full.prq"

然后我连接到互联网,并且能够通过.我在寻找prq的文本.可以通过InstallShield找到它,但是我从 community.flexerasoftware.com 询问有关4.7.2的问题.

I then connected to the internet, and it was able to go through. I looked for a text of the prq. There may be a way to find it thru InstallShield, but I found a forum post from community.flexerasoftware.com asking about 4.7.2.

感兴趣的两个部分是:

<file LocalFile="&lt;ISProductFolder&gt;
\SetupPrerequisites\Microsoft .net\4.7.1\Full\NDP472-KB4054530-x86-x64-AllOS-ENU.exe" 
URL="https://download.microsoft.com/download
/6/E/4/6E48E8AB-DC00-419E-9704-06DD46E5F81D/NDP472-KB4054530-x86-x64-AllOS-ENU.exe"
FileSize="0,0"/>

<properties Id="{BFF4A593-74C5-482F-9771-7495035EBBB0}" 
Description="This prerequisite installs the .NET Framework 4.7.2 Full standalone package." 
AltPrqURL="http://saturn.installshield.com/is/prerequisites
/Microsoft .NET Framework 4.7.2 Full.prq"/>

文件读取为"4.7.1"这一事实是我需要研究的另一种蠕虫病毒(不在此问题范围内).我假设所有的prq文件都具有相同的结构.我相信此信息告诉我URL(download.microsoft.com)被跳过,并且在安装过程中使用了AltPrqUril(saturn.installshield.com).但是,即使不跳过URL,它仍然会在万维网上查看页面.

The fact that the file reads '4.7.1' is another can of worms I need to explore (not in the scope of this question). I'm assuming all prq files have a common structure. I believe that this information tells me the URL (download.microsoft.com) was skipped and the AltPrqUril (saturn.installshield.com) was used during my install. But even if the URL were not skipped, it would still looking at a page on the world wide web.

问题

为什么需要互联网连接? 完整"版本与网络"版本特别不同,因为您无需连接到互联网即可进行安装.

Why do I need internet connection? The 'Full' version is specifically different from the 'Web' version in that you do not have to connect to the internet to install it.

推荐答案

避免Internet连接要求

要将运行时嵌入到 setup.exe 中,从而避免了 Internet连接,您可以尝试设置选项" 提取 的 setup.exe标签中的setup.exe 的先决条件" 发布视图,如下面的第二个屏幕截图所示.

To embed runtimes in the setup.exe and hence avoid the need for an Internet connection, you can try to set the option "Extract prerequisites from setup.exe" in the setup.exe tab in the Release view as illustrated in the second screenshot below.

然后在.NET Framework版本中选择" Full ". 先决条件视图.不能100%确定Installshield Express版本相对于完整版本具有哪些功能.以下是来自专业版的消息.

Then you select the "Full" .NET Framework version in the Prerequisites View. Not 100% sure what features the Installshield Express version has vs the full versions. The below is from the Premier version.

您可以通过执行" setup.exe /a "来检查已完成的捆绑销售商品- 从命令提示符-最后 setup.exe 并解压缩文件以查看捆绑包中真正包含的内容.

You can check your finished bundle, by doing a "setup.exe /a" - from a command prompt - on the final setup.exe and extract the files to see what is really included in the bundle.


快速提醒

我认为,如果您有支持协议,通常应该致电Installshield支持,或者在以下位置查看其自己的社区: https://community.flexerasoftware.com .


Quick Reminder

I think you should generally call Installshield support if you have a support agreement, or check their own community at: https://community.flexerasoftware.com.

只需提及这一点,因为人们有时会忘记检查他们是否有支持协议和支持与支持服务. 社区可能会在5分钟内解决您的问题-如果您在此处没有找到答案.

Just mentioning this since people sometimes forget to check whether they have support agreements and support & community might resolve your problems in 5 minutes - if you don't get answers here.

但是,我只是从臀部开枪,我认为原因可能是这种设置,可以在常规版本的Installshield 2018的 Release Wizard 中使用.它可能与Express版中的设置类似:

However, just shooting from the hip I would propose that the cause could be this setting that is available in the Release Wizard in the regular version of Installshield 2018. It is probably similar in the Express edition:

Release 属性页中,此设置似乎在 Setup.exe 标签下,它称为" Installshield先决条件位置". :

In the Release property pages, it seems this setting is under the Setup.exe tab and it is called "Installshield Prerequisites Location":

[

对于它的价值,我真的不喜欢肿的安装程序中包含的旧的,过时的运行时.这与我作为企业部署专家的经验有关,一天中的大部分时间都是从供应商软件包中提取过时的运行时.

For what it is worth I really dislike old, outdated runtimes included in bloated setups. This has to do with my experience as a corporate deployment specialists where much of the day consisted of extracting outdated runtimes from vendor packages.

我总是建议您从Web下载非常常见的运行时,或者允许通过Windows Update安装它们.这基本上包括所有Microsoft运行时.

I would always suggest you download very common runtimes from the web, or allow them to be installed via Windows Update. That includes basically all Microsoft runtimes.

我只喜欢捆绑运行时 1) 稀有和特殊, 2) 稳定且经过良好测试的 3) >体积小巧.即使那样,我还是希望它们单独下载并安装-以便在不重建整个安装程序的情况下安装安全修复程序-您只需在服务器上放置新的运行时版本(市场营销将需要用于物理发行的新版本-只需添加冒险,如果你问我.

I only like to bundle runtimes if they are 1) Rare and special, 2) Stable and well tested, 3) Small and well-behaving. Even then I would prefer them downloaded and installed separately - to allow security fixes to be installed without rebuilding your whole setup - you just put up the new runtime version on your server (marketing will want a new build for physical release - that is just added risk if you ask me).

战争故事 :SOAP合并模块(在过去)几乎在全球部署范围内破坏了我的程序包.部署错误增加了三倍.前提条件确实会破坏您的工作,并且您将对所遇到的问题几乎一无所知.尝试弄清楚什么中断以及为什么.并摆脱所有可能的先决条件(我知道天上掉馅饼的想法).当然,某些运行时是不可避免的.我只是逛逛:-).

War story: the SOAP merge module - back in the day - almost destroyed my package with global deployment scope. Deployment errors quadrupled. Prerequisites can really ruin your work, and you will face little understanding for the problem seen. Try to make it clear what breaks and why. And get rid of all prerequisites you can (pie-in-the-sky thinking, I know). Certain runtimes are unavoidable of course. I just ramble on :-).

这篇关于InstallShield的"Full"可再发行的力量迫使互联网接入的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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