This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Install Shield Branding - IS 2008 breaks previous conventions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 05, 2007
07:42 PM
Install Shield Branding - IS 2008 breaks previous conventions
The Install Shield Setup launcher (Setup.exe) no longer reflects the product name and version of the install package correctly.
The information provided in the "Company" and "Product Name" fields of the File Version Info of the Setup Launcher are truncated and do not reflect the correct conent. "Company" is truncated at 24 characters, while "Product Name" was correct in earlier versions, but is now truncated at 13 Characters. For example, for a product name of "Procedure Analyst", the field now says "Procedure Ana".
ALso, file version info properties are not written to the Setup launcher correctly when non-fatal errors occur in the build.
The information provided in the "Company" and "Product Name" fields of the File Version Info of the Setup Launcher are truncated and do not reflect the correct conent. "Company" is truncated at 24 characters, while "Product Name" was correct in earlier versions, but is now truncated at 13 Characters. For example, for a product name of "Procedure Analyst", the field now says "Procedure Ana".
ALso, file version info properties are not written to the Setup launcher correctly when non-fatal errors occur in the build.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 06, 2007
10:07 AM
Please see this thread: http://community.installshield.com/showthread.php?t=172965
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 06, 2007
11:03 AM
Paul
Thanks for the link to other incidents of this problem. It is obvious that this problem also existed in version 12, but not in 10.5. So, when will Macrovision fix it?
Thanks for the link to other incidents of this problem. It is obvious that this problem also existed in version 12, but not in 10.5. So, when will Macrovision fix it?