Posts Tagged ‘ISE’


I already have the ISE, do I need… ?

Monday, May 5th, 2014 by Alex Riedel
PrimalScript, PowerShell Studio or any other tool in the PowerShell universe you can think of? We get this question a lot, so I thought I’d give you a few highlights. First and foremost, this is not a game of ISE or not. The ISE is an important tool for your everyday work and you should be as familiar with it as you can. It is a far better shell then ye olde DOS style CLI (Command Line Interface) and your ideal place for shooting off cmdlets to computers near and far. It is also not a bad tool to write…   More »

VersionRecall integration with PrimalScript and PowerShell Studio

Wednesday, April 23rd, 2014 by Alex Riedel
The folks over at recently published a review of VersionRecall ( There was one paragraph that took us a little bit by surprise: “Unfortunately, PowerShell Studio doesn’t seem to recognize VersionRecall as a source control provider (at least, it didn’t show up when I tried to configure source control in PowerShell Studio). That means you can’t use the integrated check-in/out controls in PowerShell Studio. Instead, you almost want to open files by using VersionRecall’s Explorer, save them in PowerShell Studio, and then submit them to the repository back in VersionRecall. That’s a shame; the automatic check-in/out in PowerShell Studio…   More »

VersionRecall 2014 released.

Wednesday, February 12th, 2014 by Alex Riedel
We are proud to announce that VersionRecall 2014 has been released and is now available for download from our web site at If you have been evaluating the community preview version, please make sure to read all the way down so you catch the new features that have been added. If you have not seen our extended community preview, please make sure to download the trial and and find out how easy version control can be. VersionRecall 2014 is the first version control software that understands scripting in general and PowerShell in particular. Here are just some of the…   More »

Introducing SAPIEN’s VersionRecall 2014

Tuesday, June 4th, 2013 by Alex Riedel
Version control is a necessity for most, if not all, software development teams. When you work with a large number of individuals plugging away at the same code you just need some mechanism to channel access and preserve previous known-good states. Version control systems have evolved from simple check-in/check-out systems like Microsoft’s Delta and later SourceSafe to cloud-based peer to peer systems like Subversion and Mercurial, just to name a few. They all share mechanisms intended for a team of people working on code. So quite naturally it contains lots of features and elements that are not necessary for…   More »

Not all syntax coloring is created equal

Wednesday, February 13th, 2013 by Alex Riedel
Syntax coloring for programming languages was originally introduced as a visual aid to assist developers in assessing the syntactical correctness of code. Unlike the squiggly red or green underlines in Microsoft Word colors indicate validation rather than error. So while glancing at a syntax colored stretch of code the usual green hue of comments and reddish string colors enclosed in double quotes quickly instill a sense of the structure to the code. Commands are colored in certain specific colors and indicate that the system is aware of them. Traditional programming languages, like C/C++, have only a very few keywords, so…   More »

PowerShell V3 breakpoint bug

Monday, September 24th, 2012 by Alex Riedel
While we are adapting and verifying all our bits and pieces for PowerShell V3 and Windows 8, we sometimes stumble across little changes from PowerShell V2 behavior. Most of the time this is pretty simple and we can adapt our code to a new object or a change of where the information is located. Sometimes however we come across a real bug. This is one of these instances. The following has been tested in Windows 8 RTM with the PowerShell V3 ISE (64 Bit). Take the following simple script: We will put a breakpoint on line 2 and hit run:…   More »

PSModulePath discrepancies

Tuesday, May 22nd, 2012 by Alex Riedel
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 links to the per-user module path. If you query the environment variable in CMD you get the expected result: If you do the same thing in PowerShell you get a different result: Same thing happens in the ISE or any custom PowerShell host, like PrimalScript. Now, Microsoft says here to add persistent changes to the PSModulePath variable in the profile.…   More »

Fun with PowerShell ISE

Friday, April 17th, 2009 by Jeffery Hicks
A popular PowerShell version 2 feature is the graphical PowerShell console, known as the Integrated Script Environment or ISE. The ISE has its own object model which means you can customize it. Here a few things you might want to tweak, or at least experiment with.   More »