Any additional documentation on the MSI Builder?
Posted: Tue Oct 06, 2015 8:16 am
PrimalScript 2015 7.1.69
64 bit
Is there any additional information on the MSI packager? The base documentation seems incomplete. For example, by trial and error I had to discover the local installation folders.
Is there some way to make the MSI installer execute one or more of the included files as part of the installation process?
Having previously used PrimalScript 2007 and PrimalScript 2012, I am finding serious gaps with the features of the 2015 packager and MSI builder.
1. The old packagers let me compile multiple files with the script that could then be accessed by the script when it executed. The new packager appears to only compile the one script file. Is this accurate?
2. The MSI builder lets me install multiple files on the computer, but it doesn't seem to let me execute any of the installed files as part of the install. Is this correct?
What I am getting at is that it used to be a single execution step to drop files on the machine and execute a script. This was ideal for sending and executing scripts via software deployment tools. It had the added advantage of optionally cleaning up after itself. Now, it seems like it's two discrete steps to install scripts with dependent files and then execute them.
64 bit
Is there any additional information on the MSI packager? The base documentation seems incomplete. For example, by trial and error I had to discover the local installation folders.
Is there some way to make the MSI installer execute one or more of the included files as part of the installation process?
Having previously used PrimalScript 2007 and PrimalScript 2012, I am finding serious gaps with the features of the 2015 packager and MSI builder.
1. The old packagers let me compile multiple files with the script that could then be accessed by the script when it executed. The new packager appears to only compile the one script file. Is this accurate?
2. The MSI builder lets me install multiple files on the computer, but it doesn't seem to let me execute any of the installed files as part of the install. Is this correct?
What I am getting at is that it used to be a single execution step to drop files on the machine and execute a script. This was ideal for sending and executing scripts via software deployment tools. It had the added advantage of optionally cleaning up after itself. Now, it seems like it's two discrete steps to install scripts with dependent files and then execute them.