One of the most important things for any type of development is quick and efficient access to help information. No matter whether you are a seasoned developer or just started to write scripts longer than five lines, at some point you will need help.Maybe you just need a reminder about what the parameters of a […]
Category: PrimalScript
PowerShell unable to run Unicode files without BOM
A recent change in PrimalScript’s packager converts all files packaged and executed to Unicode files. If your script is a standard ANSI file it will be converted to Unicode before being packaged. Under normal circumstances you should never see any problem arising from that process except for a little hiccup that we recently encountered. If […]
Announcing PrimalScript 2011
Since the announcement of PrimalForms 2011 we have received quite a number of inquiries about the next generation of PrimalScript. So without further delay, yes, there will also be a 2011 version of PrimalScript. We have analyzed all the input we have received from you, our users, during the past two years and worked […]
Moving to 64 bit: Running PowerShell files in 64 bit from PrimalScript 2009
Last time we looked at running VBScript files in 64 bit from within PrimalScript 2009. As you may recall, the only thing required was to provide a path to the 64 bit CScript.exe or WScript.exe and substituting “sysnative” for “system32”. The rest was all automatic. As I mentioned last time, PowerShell requires some extra work. […]
Moving to 64 bit: Running VBScript files in 64 bit mode from PrimalScript 2009
PrimalScript 2009 usually uses CScript.exe to run VBScript files and captures its output and directs it to the IDE’s output windows. Since PrimalScript 2009 is a 32 bit application the host used is also of the 32 bit variety, residing in the System32 folder of your Windows directory. If you are working on a 64 […]
Reminder: Backup survey
This is a reminder for our current survey about Backup and Version Control. Please click here to participate: 2010 Backup Survey Enter your email in the survey to win cool prizes. Your responses will help determine what features get added and what gets cut from PrimalScript 2011 and PrimalForms 2011, so don’t hesitate.
Moving to 64 bit: Running a 64 bit PowerShell console inside PrimalScript 2009
PrimalScript 2009 is a 32 bit application, so by default it uses the 32 bit version of PowerShell even on a 64 bit machine for the embedded console. If you are dealing with mostly 64 bit server software you may want to make the embedded shell use the 64 bit version of PowerShell. The default […]
Scripting Toolkit ISO available for download
For some time now, SAPIEN has been distributing a free “Scripting Toolkit” CD at various trade shows and events. This CD contains copies of all of our free tools, trial versions of our paid applications, samples of our ebooks and training videos and other cool stuff. All of this stuff is available individually for download […]
RSEE now supports PowerShell
With this month’s service release for PrimalScript 2009 (build 631) we included an updated version of the RSEE (Remote Script Execution Engine) service. The new version is now available in 32 and 64 bit and can execute PowerShell scripts remotely. It is important to note that you cannot mix the new PrimalScript build with older […]
New packaging options for PrimalScript 2009
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 wrap a variety of script types into 32 bit executables. With today’s service release (5.0.627) […]
