Software Deployment

One, post in the correct forum, 'Package Development'. This forum deals with errors returned by the Windows Installer engine.

Two, go to 'Direct Editor', locate the row in the 'Binary' table and delete it. If the entry was as a result of adding a Custom Action, delete its row from the 'CustomAction' table.

Three, doesn't IS have an 'Undo' feature?

sorry for incorrect forum,

I have been exporting from binnary table one binnary file. After exporting I have forward with changes inside mst, then save and test. But I have recognize that this "exported binnary" is deleted via the mst. So when I open it in Install shield I can see on direct editon binary tabel that binary19 is strikthrought. How could I unstrikethrought the binary19 record?

Oh, wait...perhaps I misunderstood...is it that you deleted a record from the table and now you want to reinstate it?

is it that you deleted a record from the table and now you want to reinstate it? -> Yes

It's a shame IS doesn't create back-ups of files, like Wise does, eh? Now might be a good time to get into the habit of creating copies of working files before making changes...

Tricky, this one. I'd be loath to re-import the binary into the MST's Binary table, as I don't honestly know what the effct would be in having an entry in the MSI and an identical one in the MST. In your position, I'd probably:

- install Orca or InstEdit, if you don't already have them.
- copy the MSI
- open both copies of the MSI in separate Orca/InstEdit instances
- apply the "broken" transform to one instance. Usefully, the table changes are highlighted in green
- work through the changes and copy them across to the second instance APART FROM the Binary table deletion
- save the new MST

Recreation of MST have been finaly used to solve the issue. It is more comfortable to recreate MST like VBScab is navigating in the previous message.

Thank you
xxMBxx