DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
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.
Thank you for posting, email@example.com.
Did you remember to include the following?
- 1. Product, version and build (e.g. Product: PrimalScript 2014, Version & Build: 7.0.46. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
2. Specify if you are running a 32 or 64 bit version
3. Specify your operating system and if it is 32 or 64 bit.
4. Attach a screenshot if your issue can be seen on the screen
5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.
*** Make sure you do not post any licensing information ***
You can of course execute any additional scripts or executables from your main program as needed. I assume that know how to call another script or program.
The old packager was basically a self-extracting executable. It unpacked additional scripts and files when executed and deleted them optionally at the end. With modern OS versions this is mostly no longer an option. For example you cannot simply write files anywhere in C:\Program Files unless your process is elevated. Many anti-virus/malware scanners actively prevent this type of behavior from happening. This meant that the "old-style" packages failed on many modern machines and we were naturally asked to "fix this ASAP".
So we went with the procedure prescribed by Microsoft. Create an MSI installer to copy the files needed and then execute them as desired.
The advantages are the MSIs can be easily rolled out with deployment tools, they are allowed (via elevation) to write to places like C:\program Files and the end user can easily determine if a solution is installed and what version via the control panel.
SAPIEN Technologies, Inc.
Who is online
Users browsing this forum: No registered users and 8 guests