cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bharath_reddy
Level 3

How to change the fields in properties window?

Hi ,

We are using 'InstallAnywhere 2008 VP1 Enterprise' edition installer to create a installation file[install.exe] on Windows-XP operating system. After creating the install.exe file, if we right-click on this and view the properties window, the 'Version' tab is showing some fields that needs to be changed for our requirement.

The current values that are displayed and the values that we are expecting are listed below


Name , CurrrentValue , ExpectedValue
-----------------------------------------------------------------------
FileVersion , 9.0.0.0 , 4.1.0.1
Description , IA Self-Extractor ,
Company , Acresso ,
ProductName, InstallAnywhere ,



I am also attaching a snapshot[IA_Version.png] of the same for quick understanding.

In the advanced designer, Project >> Description >> Product Name and Product Id , values are reflected properly in the installer. But the problem is only when we right click on the .exe file and verify the 'Version' tab in the properties window.

If anyone has worked on this issue earlier or if you know the fix, please do let us know.

Thanks in advance,
-- Bharath
Labels (1)
0 Kudos
(1) Reply
pv7721
Level 20

Well, I don't know how many LaunchAnywheres you install, but you can do this little test: in the folder where you install'em group the files by the extension, and then check the size of the .exe files: in case you have more than one, you'll notice that even if they have different names, the size is always the same: either 114688 bytes (if your launcher is a console one) or 115712 (if your launcher is a graphical one). So what's the reason for that? Simply, LaunchAnywheres are nothing but small exes that provide a wrapper for launching the classes for your software (otherwise you would have a big clumsy line containing java invocation with the class, the classpath etc. etc.) At least on Windows it also provides a handy way for employing shortcuts. So all the intelligence is actually in the corresponding .lax file... So all this introduction to say that basically what you would like to do is not possible, as all the LaunchAnywheres are just copies of the appropriate ones located your IA installation folder, in the resource\launchanywheres\windows folder... So unless manually patching the binary file, highly unrecommended, most likely not supported, and probably against the IA EULA, I don't see what option you've got left. After all, come on, these are really IA files, so they should have IA versioning (because LaunchAnywheres change between IA versions). Do you really think that an end-user will have the time to manually check all the .exe files in order to see if they've got the correct version?!? IMHO the requirement you've got must come from an overzealous QA Engineer (easy to deflect that: not a bug) or maybe from a manager (well, this is a little bit more complicated, but you really must make them understand: these are 3rd party files, that are required for your application to work, but you're not supposed to modify them in any way). Hope this helps!
0 Kudos