When saving my IS-project, the value of the postbuild-prop "Copy to Folder" is not written to the project file. After re-opening the project, the prop is empty??!
This may be related to a bug I submitted a while back where the CopyTo entry would not take if I did not select another item in the same release prior to saving, switching to another view, or even another release. The engineering team submitted work order IOA-000038131, but I have no idea when this will be addressed.
Does anyone else get a similar problem to this with the Event Conditions on dialog boxes. I find that if I add two or more Events together, the Condition field on the last one doesn't get saved, unless I click away and then come back between each event.
This has caused no end of problems where I add two conditions, go away, and then don't find until testing that one of these conditions isn't working, only to then come back to the dialog and find the condition field blank.
This issue is resolved in the next release of InstallShield. The issue is caused by a UI bug; the actual copy to folder data is maintained in the ISRelease table but is incorrectly displayed in the Releases view.
Regarding the dialog conditions, it is possible that the grid does not end the edit you are currently making. This should be a fairly rare occurrance in recent versions of InstallShield due to some changes that were made in the grid. If you encounter this issue, try hitting after your changes have been made in the Condition field. This should end the current edit before moving to a different field or view.
- The Copy To Folder value is stored in the MediaLocation column of the ISRelease table. Note that if no value has been set for Copy To Folder, the value in the MediaLocation column will be 'MediaLocation' (the column cannot be null).
- The enter key trick is specifically for other grids in the IDE, mostly ones that appear in the Dialog Editor.
- We typically try to provide hotfixes for critical/show-stopper type issues (crashes, data loss, etc.). The Copy To Folder issue is mostly a cosmetic issue, and while it can be a nuisance, because this issue does not typically involve loss of data, it was not considered critical to the point of warranting a hotfix (this can vary from issue to issue and a hotfix cannot be guaranteed to be available).
- Work order IOC-000070835 is currently in a pending status. There is no estimated time frame for a code-based solution at this point.
