![]() ![]() The change in behaviour was seen when the set of installed files changed, we had not changed the AI file (apart from updating the product version). My suspicion is that something is going wrong with the files remove/replace stage where files are removed and not replaced. ![]() no prior installation to replace) the installation proceeds to completion. This bears out with the observed behaviour that from clean install (i.e. I've checked the InstallExecuteSequence table using Orca on the generated MSI file and the sequence numbers show that the custom actions are indeed scheduled after all the files have been installed. I have already placed the custom action after the Add Resources phase in the Advanced Installer UI 'Install Execution Stage' which is why I am surprised to see it running before the resources have been written to the final destination. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |