Thu Apr 09, 2015 1:45 am
That's actually sad Edit: unexpected.
Hey Rony, how can this behavior of the "installer" be justified in production?
Is there anything new that requires Fusion to live as singleton installation? What is it? Wouldn't it be better to finally split the default profiles and Fusion Registry Entry instead based on the major Version?
All other VFX packages can't be wrong (Maya, Houdini, ...)
I do understand that it is easier to support an application that has the same version throughout all customers, but enforcing it is the wrong approach, especially since we are dealing with professional software and not mobile apps.
As a customer I can live with "you need to update to the latest greatest to be able to take advantage of a new feature or even bugfix". But I can not live with changing a app during production that possibly breaks the show, or not being able to open older projects because the installer killed the old app. This may be ok to change versions on a machine. Now think of a cluster of workstations in a studio or a renderfarm ...
Short answer to the initial question is: Rename your initial Fusion folder before running the installer. This will not take care of anything like Links, Registry Entries etc.
Long answer:
The install logs reveal that it actually looks inside the usual internal installer database for the product code and former install location and then removes the old version in a custom Action which for whatever reason is called: InstallFinalize. So there is no way to prevent this with the usual uninstall entry in the registry.
There are ways to manipulate the installer in a way to skip this action, but it would probably be against the EULA so I do not recommend this over the renaming.
Instead please make voice to at least have an option to not uninstall former versions.