2

I'm using Installshield 2019 to generate a basic MSI file. I want to customize the file properties that are displayed in the windows explorer file properties (in the details tab => title, subject, comments) Sadly (and strangely), the Product Version does not appear in my generated MSI file's props, and I would like to have at least one file property with the product version.

Constraint: It is automated => I'm using the command line with IsBuildCmd.exe to pass the product version.

In the General Information panel of my project I can define a few values they are mapped to "Strings" (and not properties). In the release information it is the same, I can override the file properties values, but they are mapped to "strings".

1/ I don't manage to map those values to properties

2/ I did not find anything to override "Strings" from the command line

Thanks for your help

vlabatut
  • 118
  • 8
  • in my eyes it is an installshield defect, the ability to pass the "product version" as a parameter should not prevent from setting this value into the file properties. It should work naturally... case opened... – vlabatut Jul 07 '20 at 09:12

2 Answers2

1

It may be a little tough but I think you can control this using the IsWiProject COM interface. With this you can dynamically set the ProductVersion property for the project.

Doc
  • 670
  • 3
  • 16
  • This is the solution according to Flexera support. Finally I did not use the InstallShield COM interface. Our build chains were already using ISBuildCmd.exe and that was a bit too much for us to change it all. We finally used a small utility from the Windows SDK call "MsiInfo.exe" that easily did the job. Just after the MSI has been generated by InstallShield, we patch the Comment property with the product name and version. MsiInfo.exe "MyProduct.msi" /O "MyProduct v1.200.000" That was the easiest for us! – vlabatut Jul 29 '20 at 10:01
0

Try these old answers:

Short answer is that there are various options here to review. Be aware that there are some persistent bugs here and there, have a good read of the answers - particularly the problems described in the second one. Maybe run a smoke test.

Further Links:

Stein Åsmul
  • 34,628
  • 23
  • 78
  • 140