Posts Tagged ‘PrimalScript’


 

Introducing the SAPIEN Information Center

Tuesday, July 12th, 2016 by June Alane Reif
Over the years, the articles in this blog have grown extensively. There's a lot of valuable information in here, but it's become hard to find because it's mixed in with various tour announcements, special offers, conference recaps, and the like. So, we have decided to pull the important articles and place them—along with information relevant to PowerShell and scripting—in a more organized and easily searchable venue. We are proud to introduce the SAPIEN Information Center. The most recent articles are always highlighted in a list on the left side of the window. The SAPIEN Information Center currently has the following…   More »

PrimalScript 2016 service build adds CPU and memory performance graphs

Thursday, July 7th, 2016 by Alex Riedel
The latest service build of PrimalScript 2016 (7.2.91) adds performance graphs for your scripts. To enable this feature you just need to make the “Performance” tab visible before you execute your script. Performance data can be collected on any script run from within PrimalScript as long as you enabled output redirection. That means this applies to PowerShell, VBScript, Perl or any other script that you run from within PrimalScript. The output window will also display the peak values during the execution of your script when it finishes. Since collecting this data while executing your script obviously adds additional CPU and…   More »

Using Bash with PrimalScript 2016

Thursday, May 26th, 2016 by Alex Riedel
I have been asked a few times now to use Bash with PrimalScript. It doesn’t have all the setup for it out of the box because there are a few different implementations of Bash available for Windows. If you followed the latest news, Microsoft has announced at the BUILD 2016 keynote that Bash will become an integral part of Windows. (https://www.youtube.com/watch?v=kJGqZHQzNRo) Since we do not have the bits from Microsoft yet, I used the Cygwin Bash shell to demonstrate the necessary steps for PrimalScript 2016. You can download and install this version from here: https://cygwin.com/install.html There are a few quirks…   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 »

Running PowerShell Scripts: Survey Results

Monday, February 8th, 2016 by June Blender
We're always evaluating the best, easiest, and most efficient ways to write, run, and publish Windows Powershell scripts and modules. But, our starting point is always how people work now. We were curious about how PowerShell scripters, including managers, ran scripts, and how their employees ran scripts written for them.   To gather this information, SAPIEN Technologies, Inc. created an online survey about the ways in which users run PowerShell scripts. We encouraged users to participate in a blog post and several posts on Facebook and Twitter. And, people really responded. We collected 88 responses between 12/16/2015 and 1/05/2016.  …   More »

Where are v3 and v4? PowerShell Versions in PowerShell Studio

Monday, December 21st, 2015 by June Blender
In this post, we explain why PowerShell Studio can run your scripts only the versions of Windows PowerShell that are installed on local and remote computers. If you've recently upgraded to Windows 10 from Windows 7, 8, or 8.1, you'll notice quickly that you now have Windows PowerShell 5.0. Depending on your upgrade path and subsequent updates, you might be running any version of Windows PowerShell greater than or equal to 5.0.10240. Or, you might have installed the shiny new Windows Management Framework 5.0 for Windows 7 SP1, Windows Server 2008 R2, and later versions of Windows client and server. In…   More »

How do you run scripts?

Tuesday, December 15th, 2015 by June Blender
It's one of those questions that probably divides people into clans, like where you place your curly braces in a script block. Take the survey: How do you run scripts? But, it's an important question for productivity. Those of us who live the PowerShell life run scripts all the time. We might also delegate the task of running scripts to others. If the way that we run our scripts isn't efficient, we (or our delegates) lose at least some of the time we gained from automation. Some of us (okay, me) run scripts from the console. We'll open a console…   More »

Displaying Help for a Script in an Executable File

Wednesday, December 9th, 2015 by June Blender
This is the third blog in a multi-part series about designing a Windows PowerShell scripts 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 »

Passing Parameters to a Script in an Executable File

Monday, November 30th, 2015 by June Blender
This is the first 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 »

Engine Type Prerequisites

Monday, November 16th, 2015 by Devin Leaman
When building executables in PrimalScript or PowerShell Studio there are various engine types to choose from, each of them with a prerequisite that must be installed on the machine that will be running your program. For example, if you build an executable in PowerShell Studio and select the SAPIEN PowerShell V2 Host (Command Line) Win32 engine then the .NET Framework 2.0 is required on the target machine. Here is a table that shows the prerequisites for each engine type: Engine Prerequisite SAPIEN PowerShell V2 Host (Command Line) Win32 .NET Framework 2.0 SAPIEN PowerShell V2 Host (Command Line) x64 .NET Framework 2.0 SAPIEN PowerShell V2…   More »