12/01/2009 3394 views
Hi All,

I was wondering if there was a way to tweak either the .msi or the registry to set the version displayed in Add/Remove Programs to reflect the actual applications .exe version. Since Windows Installer only recognizes/used #.#.# and executables and libraries are versioned #.#.#.#, they are out of wack a bit.

I would like add remove programs to reflect instead of our install product version crunch to 1.2.44.

Then my question would be, would any change to this potentially harm the uninstall or upgrade processes due to a displayed version change.

I do see that in the registry that if I change the DisplayVersion value of HKLM\Software\Microsoft\Windows\CurrentVersion\Unintstall\{Product GUID} key, I see it reflected in ARP.

It would be nice, if a change here doesn't cause problems, I could set this in the .msi instead of setting in the registry at the end of the install.

Thoughts, pointers, pitfalls, warnings appreciated!

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

You could add the data to the ProductName property...or, as you say, change the DisplayVersion. Since they're both purely cosmetic, there are no implications that I can foresee.
Answered 12/01/2009 by: VBScab
Red Belt

What I was thinking of doing was to create a custom action near the end of the install to tweak this registry value. Will I still have [ProductCode] available to me in the Execute Deferred sequence sometime before InstallFinalize?
Answered 12/01/2009 by: Superfreak3
2nd Degree Black Belt

You can change the productname (as shown in Add/Remove Programs) in the registry:

You can change the version (as shown in Add/Remove Programs)in the registry:
Answered 12/01/2009 by: yuri
Orange Belt

Will I still have [ProductCode] available to me in the Execute Deferred sequenceLuckily for you, PC is one of the 3 properties which are "natively" available in that sequence, viz. CustomActionData, ProductCode and UserSID.
Answered 12/02/2009 by: VBScab
Red Belt

I know now. I ran a simple little install with an action to display ProductCode right before InstallFinalize and I SAW THE CODE!!!!

Answered 12/02/2009 by: Superfreak3
2nd Degree Black Belt

If you use a tool like Wise it is also possible to run it in debug mode. You could use a number of breakpoints to see if certain properties still exist.
Answered 12/02/2009 by: yuri
Orange Belt