There is another option if you need both 32-bit and 64-bit versions of your application: “Microsoft Windows Native”. The folder names are x86 for 32-bit, and 圆4 for 64-bit. In the latter case, the packager will create a packaged executable for each platform in a different folder. If you need a 32-bit version of your application, you can select “Microsoft Windows 32 Bit”, or “Microsoft Windows 32 and 64 Bit”. Unless you still have some 32-bit computers in your network, you can usually set this to 64-bit and not worry about it. The platform choices of 32-bit and 64-bit are pretty simple. Please note that these options have to be selected and saved before you can build a package the build button will remain inactive until you have specified the minimum required settings. But if you have any questions, please feel free to comment below.īefore you can package any script, you need to tell the packager which platform you intend to run the script under (32-bit, 64-bit, or both), and the PowerShell version. Long-time users of PrimalScript are commonly aware of the options for VBScript, JScript, Windows Script Host, etc., so we will skip these. But fear not most items have a reasonable default and those that don’t are actually not that complicated.įor this article series, we will focus on PowerShell. When you open the SAPIEN Script Packager for the first time, the number of options can be a bit daunting. This first article in our SAPIEN Script Packager series walks you through the Script Engine settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |