The latest in our video series demonstrates how to to create a Windows Service to kill a Solitaire process using SAPIEN’s PrimalScript 2018. In this short video we show you how to build and install a PowerShell Windows Service, including: Create a Windows Service from a PowerShell Service Template Add the code from a custom […]
Tag: Packager
PrimalScript and PowerShell Studio featuring Axialis icons
Not too long ago we added a collection of icons to PrimalScript and PowerShell Studio to give you some more options for your packaged executable files: Stock Icons for your Script Packages We are very pleased to announce that we now include a good number of high quality and modern looking icons made by Axialis with […]
New PowerShell Service Template for PrimalScript 2018
PrimalScript 2018 supports advanced functionality for Windows services written in PowerShell and packaged with PrimalScript 2018 or PowerShell Studio 2018. While your old code will still work unmodified with this packager engine as it detects the presence of the new functions, it is a good idea to revamp your code to use the new template. […]
Creating a system tray application with PowerShell
One of the great benefits of PowerShell is the ability to very quickly retrieve system information and metrics. We have added three new packager engines to PowerShell Studio and PrimalScript to make it easier to present or log that information in a standard way. I have already discussed the new Windows Application engine here: https://www.sapien.com/blog/2017/06/14/new-script-engines-for-windows-powershell/ […]
New Script engines for Windows PowerShell
One of the more common tasks for an administrator is to write a script for a helpdesk employee or a fellow admin who is maybe not so PowerShell savvy (yet). Many of you like to package that script as an executable file to prevent the user from “experimenting” with your code and messing things up […]
PowerShell Studio 2016 – Service Release v5.3.130
Today we release a new build of PowerShell Studio 2016 and it includes some major changes and new features. Project Changes and Compatibility IMPORTANT: This build will convert your projects and create a backup of the original (*.psproj.bak). The new project version is not backwards compatible with older builds of PowerShell Studio. We made […]
SAPIEN Script Packager updates and new features.
The Script Packager in PrimalScript 2016 gets an update with the next service build (7.2.95). Since this service build changes the locations where your executable files are generated and some new options are available, we thought we’d let you know about these changes before they are actually released. Based on your feedback, the script engine […]
Distributing files with your packaged scripts
We get this question every week: Why can I not include my data files, secondary scripts, modules, other executables etc. with the packaged executable and have it unpack them when I run it? If you have been a SAPIEN customer for a few years you may remember that we had this feature in the packager […]
Parsing Parameters for a Script in an Executable File
This is the second blog in a multi-part series about designing a Windows PowerShell script that will be packaged in an executable file. Passing Parameters to a Script in an Executable File explains how to use the special parsing features of PowerShell Studio and PrimalScript to make passing parameters easy for PowerShell users and authors. […]
PowerShell Studio 2015 – New Collection Project deployment options
With release of the v4.2.83 build of PowerShell Studio 2015, we introduced new features that we are covering in detail over a series of articles. PowerShell Studio 2014 introduced the new Collection Project: https://www.sapien.com/blog/2014/07/29/powershell-studio-2014-collection-project/ The Collection Project simply groups various files without creating a single script as in a normal project and each script file […]
