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 […]
Category: VBScript
Throwback Thursday: Making batch files into executables
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 […]
PrimalPad 2014: User tools are back
With the 2012 release of the ever popular PrimalPad, our portable PowerShell and VBScript editor, we switched to the now almost ubiquitous ribbon user interface. One thing that disappeared because of that was the custom user tools menu. Mostly because, well, there was no menu to edit anymore. The “User-defined Tools” ribbon group is pre-filled […]
WMI Explorer 2014 released!
The latest version of the WMI Explorer is available now on our website. Here are just a few highlights from the features in this release: Superior performance using cached data and multi-threaded code gets you results fast Explore and query local and remote machines. A large variety of search options enables you to access the […]
PrimalScript 2014: VBScript gets a debug console
One of the many things on our users wish list was the ability to change variables while debugging. While we where looking to solve that, we also looked for a way to call functions while stopped at a breakpoint or execute any arbitrary code that may help facilitate testing and debugging. Since we already have […]
But it works on my machine…
We have all heard that phrase. We have all faced that scenario. A script runs perfectly fine on your machine or any VM you have, but just refuses to do anything useful on that one server where it really matters. Error messages can be notoriously unhelpful. “Access denied”, yes, but to WHAT and WHY? And […]
PrimalScript or PowerShell Studio?
We do get this question from users new to our software quite frequently. We realize that there is some overlap between the two products, they are both editors after all and both support PowerShell. I could go on and explain at length what the differences are, but fortunately I don’t have to. Powershell guru and […]
Jazz up your VBScripts with PowerShell and Windows Forms
Sure, you are supposed to write all new scripts in PowerShell. Some say you can replace any VBScript with a single line in PowerShell. But the truth is, many of you still have to maintain, develop and debug scripts written in VBScript. Some of our customers also have to maintain VBScript or JScript files that […]
PrimalScript 2012: What’s new? (Part 7)
Last time we told you about some new debugger features in PrimalScript 2012. And you already know all about the new Ribbon user interface this new version sports. One thing that we were really focused about in this version was to make navigating your code easier. Since there is no “PrimalSense” toolbar anymore the method […]
PrimalScript 2012: What’s new? (Part 6)
VBScript users have told me on occasion that they are really jealous of one feature of PowerShell: Write-Debug Depending on the value of $DebugPreference this produces output when needed but makes it easy to silence diagnostic output once a script moves to production. VBScript and JScript developers have to sprinkle WScript.Echo calls through their code […]
