When building a source distribution or application (and some others), we can specify "pre/post build actions", i.e. VIs that are called before or after the build steps.
Sadly, this option is missing when building an installer. We can only specify executables that run before of after installation, not before/after the build process.
I can think of many scenarios where a "pre/post build action" could be useful when building an installer. For example every time I build an installer, I rename the created "Volume" folder to something else, and every time I edit the setup.ini file to change the "WinFastStartup=1" to "WinFastStartup=0" (long story). These are steps before/after the build, and occur well before distribution and installation.
After "build all", I also move all new builds (source, exe, installer) to a new and unique folder, and since the installer is the last build, even this could be automated if we had post built action when building installers.
Am I missing something obvious?
(Of course I can write a VI that does all the builds and then applies the actions. Just wondering why the built-in tools are missing this functionality).