I have tested this many times and kept chasing errors that didn't exist because the save of the command line for a launch installed file custom action wasn't saving. I have made a command line change, saved component , did the build . checking the logs the change that I saved in the new build was not saved. I now do a save close the app go back in see that it didn't change , I do a save a second time close the app reopen it and then the save happened. I believe this to happen in other fields as well as when I am testing new builds sometimes getting the same error until after I have don the save at least twice.
I'm not sure why this happens. I've tested your scenario using our last version (10.5.2) of Advanced Installer, but I cannot reproduce the behavior. Can you reproduce the behavior in a new project? If so, can you please send us a sample reproducing the behavior or a test case scenario so we can test and investigate this?
Ok I will send one tomorrow , I have found this to be true of other areas as of just now I changed a a value in an ini file and rebuilt the project and it still wrote the old value in the ini file. I am not sure what is happening either as I really do like this product and have recommended it to 3 other companies with whom I do contract work. I presently hit the save button 3 times close the app and re-open to be sure the value has changed. I am thinking things are being cached . What is the difference between build and rebuild . I always use rebuild thinking that would resolve the problem but that didn't change the behavior.
If you have enabled caching in Advanced Installer option, Advanced Installer will store and reuse the cache archives it creates when you are using the [Build] operation. Using the [Rebuild] operation you will perform a clean build without reusing cached archives.
FOLLOW US
Get the latest news in Application Packaging