MSI 安装问题

发布于 2024-07-08 13:03:41 字数 372 浏览 10 评论 0原文

我有一个基于 MSI 的安装,根据我的安装打包软件(Wise Package Studio 7.0 SP2)将其打包在 EXE 文件中。

我对安装进行了许多更改,每次测试它们时,它们都工作得很好......到目前为止。

我更改了安装完成时对话框上的一些文本,现在看来,无论我如何/从何处运行安装,它都不会采用我的“新”版本。 它继续“认为”它已经安装,甚至在删除/修复/修改结束时显示我的对话框文本的旧版本。

这几乎就像将 MSI/EXE 缓存在某处,而不是运行我重新编译的(并修复了消息/进行了更改),它继续从某处运行“旧”的。

知道要检查什么/这里可能发生什么吗? 是否有 windows 文件夹我需要去检查? 我用的是XP SP2。

I've got an MSI based install that I've wrapped in an EXE file as per my installation packaging software (which is Wise Package Studio 7.0 SP2).

I've made many changes to the install, and every time I've tested them, they've worked just fine... up until now.

I changed some text on a dialog box for when the installation finishes and now it seems that no matter how/where I run the installation from, it won't take my "new" version. It continues to "think" it's already installed and even shows an older iteration of my dialog text at then end of the removal/repair/modify.

It's almost like it's cached that MSI/EXE somewhere and instead of running the one I've recompiled (and fixed the message/made changes) it continues to run the "old" one from somewhere.

Any idea what to check for/what could be going on here? Is there windows folder I need to go check? I'm on XP SP2.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

空城仅有旧梦在 2024-07-15 13:03:41

尝试在不同的机器上运行,这肯定会排除任何本地缓存。

检查您所做的更改是否确实在 MSI 中。 (使用 Orca 来执行此操作。)

Try running on a different machine, this will definitely rule out any local caching.

Check that the changes you have made are actually in the MSI. (use Orca to do this.)

神也荒唐 2024-07-15 13:03:41

好的,所以我使用 XP 虚拟机进行了尝试,并在安装前拍摄了快照。 看起来以前的安装不知何故已损坏,并且以某种方式在我正在使用的原始测试计算机上缓存自身。

通过使用干净的新电脑,我的更改就在那里并且脚本按预期工作。 现在,我不知道发生了什么导致安装像 PC 上的某个地方一样缓存,但至少我找到了解决方案。

如果我可以追踪到缓存文件的位置,我将更新这个问题......

Okay, so I tried this using an XP VM and taking a snapshot before installing. Looks like somehow the previous install was corrupt and was somehow caching itself on the original test computer I was working with.

By going to a clean and fresh PC, my changes were there and the script worked as expected. Now, I don't know what happened to cause the installation to cache like that somewhere on the PC, but at least I found a resolution.

I'll update this question with the location of the cached files if I can track them down...

酒儿 2024-07-15 13:03:41

要删除任何缓存的 Windows Installer 信息,您可以使用 MSIZAP< /a>. 不确定 WISE,但 InstallShield 通常配置为在每次重建时自动更改软件包代码。)

我的猜测是您没有更改软件包代码,因此 Windows 将其视为相同版本的安装程序(我 至于缓存文件的位置,这是可配置的,因此在 WISE 中搜索一下,您应该可以找到它。

To remove any cached Windows Installer information, you can use MSIZAP. My guess is that you haven't changed the package code so windows sees it as the same version of the installer (I'm not sure about WISE, but InstallShield is usually configured to automatically change the package code each time you rebuild.)

As far as the location of the cached files, this is configurable so have a hunt around in WISE and you should find it.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文