I created a test project (native engine enabled) and installed a single file with DELAYUNTIL_APPLYCHANGES set to its default TRUE. When I executed the Install Files statement it naturally worked and was stacked up for installation until Apply Install was executed.
I then set DELAYUNTIL_APPLYCHANGES to FALSE. When it hit the Install Files statement it threw an error message telling me my TARGETDIR path did not exist. That's what I was hoping would happen as my Install Files statement was referencing TARGETDIR which would not be created until after Apply Install was executed.
The more I think about the native engine the more certain I am that it gives you an unparalleled paradigm for doing things that previously could not be done within the confines of the MSI architecture or at least, done, but with some difficulty. Now, there's a new way of looking at installations. It's curious for sure but has a lot of potential.
IA10: DELAYUNTIL_APPLYCHANGES
IA10: DELAYUNTIL_APPLYCHANGES
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
InstallAware MVP
Who is online
Users browsing this forum: No registered users and 44 guests