perUser 安装程序如何处理 perMachine 旧版本的程序? [英] How can a perUser installation program deal with a perMachine older version of the program?
问题描述
这类似于这里提出的问题:如何在将 InstallScope 更改为perMachine"后修复 wix 设置的升级逻辑
This is similar to the question asked here: How do I fix the upgrade logic of a wix setup after changing InstallScope to "perMachine"
仅在我们的例子中，旧版本是perMachine"，新版本是perUser".
Only in our case, the old version is "perMachine" and the new version is "perUser".
我理解您为什么不希望 perUser 安装弄乱可能在多个用户之间共享的程序.但我们需要沿着这条路走下去.
I understand why you would not want a perUser installation to mess with a program that might be shared among several users. But we need to go down this path.
目前，我们通过在注册表中挖掘并拒绝安装来检测旧程序的版本，除非他们先卸载旧版本.这不是真正的用户友好.
Currently, we are detecting versions of the old program by digging around in the registry and refusing to install unless they uninstall the old version first. It isn't real user friendly.
有没有更好的技术?
推荐答案
我永远不会更改为每个用户的设置，出于很多原因，我宁愿从每个用户更改为每台机器.为什么需要每个用户?
I would never change to a per-user setup, I would rather go from per-user to per-machine for an awful lot of reasons. Why do you need per-user?
您可能会查看我写的关于如何使用 Installshield 从每用户迁移到每台机器的描述.走另一条路也应该是可能的 - 但我认为不推荐:https://stackoverflow.com/a/12291807/129130
You might have a look at a description I wrote up on how to migrate to per-machine from per-user using Installshield. Going the other way should be possible too - but not recommended in my opinion: https://stackoverflow.com/a/12291807/129130
更新:由于这被否决了，这里有更多的链接来解释每个用户设置的一些问题.它们是真实的，我只是想警告人们他们最有可能面临的问题(几乎肯定会面临):
UPDATE: Since this was down-voted, here are a few more links to explain some of the problems with per-user setups. They are real, I am only trying to warn people what problems they are most likely going to face (almost certainly going to face):
这篇关于perUser 安装程序如何处理 perMachine 旧版本的程序?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
