将InstallShield从2009年升级到2016年的问题

I have upgraded InstallShield successfully from 2009 standalone build to 2016 standalone build. Currently using "InstallShield 2016 Standalone build" to build my package. Before creating the package i have kept a check to verify whether "InstallShield 2016 Standalone build" is installed in the system". Below is the .js code.

我已成功将InstallShield从2009年的独立版本升级到2016年的独立版本。目前正在使用“InstallShield 2016 Standalone build”来构建我的包。在创建包之前，我一直检查以验证系统中是否安装了“InstallShield 2016 Standalone build”。下面是.js代码。

try
   {
      var testStanAloneBuilder = new ActiveXObject("IswiAuto23.ISWiProject");
      delete testStanAloneBuilder;
   }
   catch (e)
   {
      ErrorExit("ERROR: The required InstallShield Stand Alone Builder is not installed.");
   }

The exception error message received is "Automation server can't create object". Can anybody please let me know if i need to do any post installation settings after installing InstallShield 2016 stand alone build.

收到的异常错误消息是“自动化服务器无法创建对象”。在安装InstallShield 2016独立版本之后，任何人都可以告诉我是否需要进行任何安装后设置。

1 个解决方案

#1

I haven't used IS in a few years but here's a few tips that should help.

我在几年内没有使用过IS，但这里有一些应该有用的提示。

1) The SAB exposes the automation interface as an optional feature to install. It might not be installed.

1）SAB将自动化界面公开为可选的安装功能。它可能没有安装。

2) The automation interface only supports 32bit. You'll get errors trying to use it from a 64bit process. (For TFS builds I select x86 msbuild platform ).

2）自动化接口仅支持32位。尝试从64位进程使用它时会出错。（对于TFS构建，我选择x86 msbuild平台）。

3) You should be able to have different versions of the SAB installed on the same build machine. (Or create different classes of machines even better.)

3）您应该能够在同一个构建计算机上安装不同版本的SAB。（或者更好地创建不同类别的机器。）

4) I like to setup parallel builds when trying out new versions of InstallShield. You should be able to keep the .ISM at the old schema and build it with both engines. (The newer SAB will upgrade the shema during the build.) Once everything checks out you can update the .ISM to the latest version of InstallSield.

4）我喜欢在尝试新版本的InstallShield时设置并行构建。您应该能够将.ISM保留在旧架构中并使用两个引擎构建它。（较新的SAB将在构建期间升级shema。）一切都检出后，您可以将.ISM更新到最新版本的InstallSield。

#1