I'm hoping someone can give me some advice or options for this scenario.
Background:
We have an existing product out in the field. That version's installer was made by Visual Studio and is MSI-based. We allowed users to choose the installation type ("Everyone" or "Just Me"), but we defaulted it to "Just Me". Therefore, a majority of installations are on a per-user basis, but we know a few have installed for "Everyone".
We're exploring the use of Advanced Installer for our new version which is still in development. We have changed A LOT of the installed files (some new, some renamed, etc) and we need to do a complete uninstall of the current version of the product before installing this new one. If we don't, we get a horrible mix of old and new files in the same application folder and our product doesn't run correctly. It's a mess.
I've used the Upgrade Code from the previous version's installer in my test AI project.
Problem:
If I install the new version with the same installation type (per-user or per-machine), the old version is properly detected and removed just like it needs to be. But if I don't match the installation type, I get the bad scenario I outlined above.
As I said earlier, the vast majority of field installations will be per-user, but I know for a fact some users have installed per-machine. Therefore locking the AI installer to per-user only isn't going to work.
Ideal Solution:
I'd REALLY love to let AI use the "Per-machine if user is administrator, per-user otherwise" setting, and still guarantee the previous version in uninstalled, regardless of that version's installation type. That may not be realistic, but I wanted to make that known.
Acceptable Solution:
I'd be okay if AI could detect the previous version's installation type and automatically set its own type accordingly. We'd be honoring a previous decision made by the user, and at the same time ensuring the previous product is properly removed.
Do Not Want:
WHAT I DO NOT WANT is to give the users a choice, because inevitably someone will choose wrong and we'll get support calls about botched installations. Plus, this new version has a lot of client and customer anticipation around it and we want to do everything we can to make it a great experience from the very start.
That's it. I sure hope someone can help me out!
Regards,
Chris
P.S. Why is there so much difference between per-user and per-machine installs? It all comes from the same installer; I don't understand why this process has to be as complicated as it's turned out to be.
FOLLOW US
Get the latest news in Application Packaging