Welcome back. As we previously discussed, PrimalScript 2014 has a few new options for the script packager and has added features for creating MSI databases and deploying your script solutions.
If you have missed the previous three installments, use the…
Read More
The last time we looked at the new installer option in PrimalScript 2014. You can find the article here: http://www.sapien.com/blog/2014/04/07/from-script-to-server-deploying-solutions-with-primalscript-2014-part-2
If you look at the deploy tab again, you will see a “Deployment” group. These functions will help you distribute…
Read More
Last time we looked at the new packager options in PrimalScript 2014. You can find the article here: http://www.sapien.com/blog/2014/03/25/from-script-to-server-deploying-solutions-with-primalscript-2014-part-1
If you look at the deploy tab again, you see an installer group that was not an option in any of…
Read More
If you take a look at the new 2014 version of PrimalScript you will discover a new tab on the ribbon interface: “Deploy”
This tab combines three major stepping stones for deploying your scripting solutions:
1. The Script Packager that…
Read More
The Script Packager has been a key feature of PrimalScript for many years now. Devised originally in the Windows 2000 era, it has some features that simply are no longer relevant or applicable in modern Windows versions. As many of…
Read More
The original The Packager and Command line Arguments blog article discussed how to pass parameters to a packaged executable. In this article we will revisit this subject and update the functions introduced in the previous article. The article will also…
Read More
If you package your script with PrimalScript’s or PrimalForm’s packager you have the option of including a manifest. This manifest can be used to make your executable file prompt for elevation when executed.
It’s easy to spot the difference between…
Read More
The latest builds of PrimalScript 2009, PrimalScript 2011, PrimalForms 2009 and PrimalForms 2011 contain a new option for running packages under different credentials. Just as the VBScript and JScript packages have done for some time now, the PowerShell engines now…
Read More
As 64 bit Windows versions become more common, you need to deploy scripts automating 64 bit software as well as maintaining 32 bit versions of the same script.
PrimalScript 2009 has always included a script packager that allowed you to…
Read More
Per forum request, this blog provides examples of how to access the packager’s command line arguments as well as provide some useful functions to parse the contents. These examples apply to PrimalForms 2009’s Packager and as well as PrimalScript 2009’s…
Read More