Posts Tagged ‘Packager’


 

PowerShell Studio 2016 – Service Release v5.3.130

Tuesday, November 15th, 2016 by David Corrales
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 changed to our projects in order comply with the best practices and warning produces by PSScriptAnalyzer. Previously, when you invoke a GUI or script file from a project, you had to use a reference function that used a Call verb. For example: Call-MainForm_psf The Call…   More »

SAPIEN Script Packager updates and new features.

Monday, October 24th, 2016 by Alex Riedel
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 selection in the Packager settings was too confusing. So we updated the user interface to minimize the number of selections and provide you with a preview of what this selection will do. Furthermore, as many of you indicated that you still need to support 32…   More »

Distributing files with your packaged scripts

Tuesday, March 22nd, 2016 by Alex Riedel
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 until the 2012 version. The predominant operating system at the time was Windows XP and this worked fine. With the advent of Windows Vista and Windows 7 we received this question more and more: “Why does my packaged script no longer work?. You need…   More »

Parsing Parameters for a Script in an Executable File

Monday, December 7th, 2015 by June Blender
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. Parsing Parameters for a Script in an Executable File explains how to parse parameters manually for special uses. Displaying Help for a Script in an Executable File explains how to display help for a script in an executable file. Output from a Script in an…   More »

PowerShell Studio 2015 – New Collection Project deployment options

Wednesday, May 6th, 2015 by David Corrales
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 runs individually. With this release, new options were added to the Collection Project in order to accommodate your deployment needs by controlling the behavior of the Packager, MSI, and Deployment as a whole or as individual files. OK Two new project properties were added: Deploy…   More »

What’s new in PrimalScript 2015?

Thursday, March 19th, 2015 by Alex Riedel
Our 2015 versions have been out for a while and most of you already know about some of the new features. But we want to make sure you don’t miss anything, so here is a brief recap. PrimalScript 2015 now has a PowerShell dialog editor If you create graphical user interfaces (GUI) in PowerShell all the time, you probably already have SAPIEN PowerShell Studio. But if you just want to create a dialog here or there to prompt for some user input or display a particular piece of data as output, you do not need to create full-fledged event driven…   More »

Throwback Thursday: Making batch files into executables

Thursday, October 30th, 2014 by Alex Riedel
PrimalScript 2014 can make a variety of script files into executable files. We call that packaging. This feature is mostly used by VBScript and PowerShell administrators to wrap their scripts into an executable file that can be shipped to end users and prevent prying eyes from seeing what makes the magic happen. For the aforementioned VBScript and PowerShell scripts this usually means a package that executes the code in memory, without the use of a temporary file. We did however receive quite a number of requests lately to also package Batch or CMD files. Here is where the “Throwback Thursday”…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 4)

Monday, April 21st, 2014 by Alex Riedel
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 links below to catch up. From script to server – Deploying solutions with PrimalScript 2014 (Part 1) From script to server – Deploying solutions with PrimalScript 2014 (Part 2) From script to server – Deploying solutions with PrimalScript 2014 (Part 3) Today we are putting this all together and show you how to use this efficiently in your day-to-day operations.…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 3)

Monday, April 14th, 2014 by Alex Riedel
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 your solutions to your target audience.   First lets look at the settings. There are two items that are mandatory. You need to have at least one file that gets deployed. If you look at the combobox, there are three items in it: Depending on what else you have defined for your solution, the initial file to deploy can either…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 2)

Monday, April 7th, 2014 by Alex Riedel
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 the previous PrimalScript versions This new feature allows you to wrap your scripts, packaged executables, associated scripts, modules, configuration and binary files in a proper Microsoft Windows Installer database for easier deployment. If you have participated in our MSIWizard community preview you may already be familiar with a lot of this. Let’s examine the options we have. Most of the…   More »