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
- :
- Modifying string tables
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
Jun 03, 2008
11:04 AM
Modifying string tables
We have recently migrated from InstallShield 5.5 to 2008. This is an InstallScript project.
In the past, we built our project through a nightly build. A perl script modified our string table with an incremented version number, and whatever version number our database was at, and then built the project with the new string table.
I don't even see the string table file in the folder structure anymore after we went through the conversion-- it seems that the only way to modify that table is to do it inside InstallShield.
Is there any way around this dilemma? Any suggestions as to where we could put that build number so that InstallShield can access it?
In the past, we built our project through a nightly build. A perl script modified our string table with an incremented version number, and whatever version number our database was at, and then built the project with the new string table.
I don't even see the string table file in the folder structure anymore after we went through the conversion-- it seems that the only way to modify that table is to do it inside InstallShield.
Is there any way around this dilemma? Any suggestions as to where we could put that build number so that InstallShield can access it?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 03, 2008
12:08 PM
You need to use InstallShield Automation here. I have seen some functions in InstallScript using which you can import and export the String table (.txt file) before building the final release.