I still don't have enough experience in the field of deployment, so perhaps I use some concepts wrong.
We have two merge modules, a .NET module and a module with shared native dlls and COM components (shared module). The msi installer contains both of them.
The versions of the .NET module is installed side-by-side, however, we would like always the latest version of the shared modules to be installed.
That's why I tried to use version comparison as I found in this forum topic:
http://www.advancedinstaller.com/forums ... f=1&t=6912.
I attached each modules to separated features in order to disable the shared module if it's not necessary to be installed based on conditional install level. The shared module puts its version number into the registry, and the msi compares that version number with the current one.
Now I suppose I should put each component of the version number separately into the registry for correct comparison.
Or should I create a separated msi installer for the shared module with auto upgrade?
Thanks,
Gabor Vasko
FOLLOW US
Get the latest news in Application Packaging