iPowerShell Pro uses two mandatory files to display cmdlet help: the PowerShell Help Formatted XML file and an automatically generated .index file. We also use three optional files: a user-generated .info file and two user created .png files.
The .xml…
Read More
iPowerShell Pro initially ships without any cmdlets, etc. You should connect to Wi-Fi to download the initial data set, as the V3 cmdlet set is quite extensive and can take a couple of minutes to download.
Downloading the data onto…
Read More
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.…
Read More
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…
Read More
Windows 8 by default includes PowerShell V3 installed, which is now an essential part of the operating system and cannot be removed. PowerShell V2 on the other hand is a different story. The default installation should have PowerShell v2 installed…
Read More
Some of you may have already encountered this. You upgraded your system to PowerShell 3.0, 4.0, or 5.0 and you want PrimalScript or PowerShell Studio to recognize the new version of PowerShell. This article addresses that very question. You can accomplish this by…
Read More
If you follow the Spotlight on Controls series you might be familiar with the Enable property that is shared by all WinForms controls. This property allows you to disable controls so they no longer can be interacted with.
For example,…
Read More
The original The Packager and Command line Arguments blog article discussed how to pass parameters to a packaged executable. In this article we will revisit this subject and update the functions introduced in the previous article. The article will also…
Read More
A week ago I was hanging out with PowerShell trainer extraordinaire Jason Helmick and while we where geeking out over PowerShell tricks and software features (yes, I know, bad, isn’t it?) I asked him how he would improve file groups.…
Read More
While investigating a bug report about ChangeVue’s installer we stumbled across a discrepancy with PowerShell’s PSModulePath environment variable.
On a virgin Windows 7 machine the environment variable is set to “C:\windows\system32\WindowsPowerShell\v1.0\Modules\” via a System Environment Variable.There is no default that…
Read More
