Build does not always include new source file/script version - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

MABLINK
Posts: 4
Joined: Wed Nov 18, 2009 8:56 am

Build does not always include new source file/script version

Advanced Installer 7.5.2 build 26791:

I've been having an issue where doing a new build does not pull the latest "Source File" from its defined source.

For example, I add a temporary file to the installation project and later change the source file (Not the source name). The next time I do a build it does not include the “New” source file, but rather still has the old one. I have to remove the reference and add the temporary file back to the project for it to be included in the build.

I would expect that performing a build will ALWAYS get the files from the defined source.

I did find the Project Options Settings for Build Caching, but even with this turned off, it does not pull the latest file from the source during a build.

I also found this behavior in SQL Scripts. The new file wasn't included unless I selected it again.

Is there an option I may be missing to ALWAYS force a build to pull files from their source?
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Build does not always include new source file/script version

Hello,

Unfortunately I could not reproduce this behavior. What I tried was:
- added a new temporary text file to the project
- created a custom action that would launch that text file in notepad
- the text file had some text written in it
Upon running the installer, the custom action launched the text file in notepad, and the expected text was displayed.
I then went back to the Files and Folders page and double clicked the temporary file. Changed the source path field to the path of some other text file named the same as the previous text file, but with different content in it.
Built the installer again, ran it. As expected, the custom action launched the temporary file, which displayed the new text as expected.

Perhaps I am not testing this right.
Could you be so kind as to create a sample project which I can build and test on my machine? If so, please send it to support at advancedinstaller dot com or attach it here on the forum.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”