Archive for the ‘VBScript’ Category


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 »

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 »

PrimalPad 2014: User tools are back

Wednesday, September 17th, 2014 by Alex Riedel
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 with the Windows Registry Editor, the Control Panel and the Computer Management plug-in, just to not have an empty group stare back at you. Click on the launch button in the group to edit the tools to your desire. Launch button Tool edit dialog As…   More »

WMI Explorer 2014 released!

Thursday, April 17th, 2014 by Alex Riedel
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 information you need faster and more precisely. Filters allow you to reduce noise and focus only on relevant information. Preset and custom queries let you not only examine the classes, properties and methods but also the underlying data. View all documentation for any WMI object…   More »

PrimalScript 2014: VBScript gets a debug console

Monday, March 31st, 2014 by Alex Riedel
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 a debug console doing that exact same thing for PowerShell, we thought it would be best to do the same thing for VBScript and JScript. So now setting a variable or an objects property is as easy as typing it into the console. Call functions,…   More »

But it works on my machine…

Thursday, May 16th, 2013 by Alex Riedel
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 everyone’s favorite “Unknown error” makes for a very frustrating day at the office. If you have physical or remote desktop access to that server it’s pretty easy, just use whatever debugger you have, install it on that machine and see what happens. Or, in case…   More »

PrimalScript or PowerShell Studio?

Wednesday, April 10th, 2013 by Alex Riedel
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 trainer extraordinaire Jason Helmick just released an excellent overview and video about what to choose for what and why. So, lean back, read the article and watch the video.  Click here for the blog article  Click here for the video…   More »

Jazz up your VBScripts with PowerShell and Windows Forms

Tuesday, March 12th, 2013 by Alex Riedel
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 run under a custom host, automating some server application that likely will never be changed to use PowerShell. And, judging from some emails we get, you cast a jealous look at this new fangled Windows Forms stuff the PowerShell crowd uses to make great tools.…   More »

PrimalScript 2012: What’s new? (Part 7)

Wednesday, May 9th, 2012 by Alex Riedel
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 combo box that enabled you to jump between functions needed to find a new home. If you load a file into PrimalScript 2012 you will notice the two new combo boxes on top of the edit window: The right-hand combo box serves as an indicator…   More »

PrimalScript 2012: What’s new? (Part 6)

Monday, May 7th, 2012 by Alex Riedel
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 and then go and comment them out before handing the script off. In a large script with hundreds or even thousands of lines that can be a daunting and error prone task. You don't want to disable real output and not forget any diagnostic output.…   More »