Archive for the ‘Software News’ Category


 

Using Bash with PrimalScript 2016

Thursday, May 26th, 2016 by Alex Riedel
I have been asked a few times now to use Bash with PrimalScript. It doesn’t have all the setup for it out of the box because there are a few different implementations of Bash available for Windows. If you followed the latest news, Microsoft has announced at the BUILD 2016 keynote that Bash will become an integral part of Windows. (https://www.youtube.com/watch?v=kJGqZHQzNRo) Since we do not have the bits from Microsoft yet, I used the Cygwin Bash shell to demonstrate the necessary steps for PrimalScript 2016. You can download and install this version from here: https://cygwin.com/install.html There are a few quirks…   More »

Add custom tools to the menu

Monday, May 23rd, 2016 by June Blender
There are so many features in PowerShell Studio and PrimalScript that I think I can't live without, like the Format Script button, file groups, and conditional breakpoints. But, there are few features I'd love to have that aren't there. They're easy enough to add, but they're really personal to me. Fortunately, I can add them myself. What is a custom tool? The Custom Tool feature in PowerShell Studio and PrimalScript lets you define commands in an INF file and add them to a menu. For example, I have huge Scripts library on One Drive where I keep all of my…   More »

Property Pane: Change property values of multiple objects

Friday, May 20th, 2016 by June Blender
Sometimes, I say things so many times that I start to believe them, even when I'm wrong. Here's a correction of one of the details that I've gotten wrong repeatedly. "You can only use the Properties pane on one object at time." -- me Um, no. The Properties pane in PowerShell Studio displays the properties and property values of an object, that is, one of the Windows Forms controls on the Designer pane. By default, it displays the properties of one object at a time. To determine which object the Properties pane displays: In the Designer pane, click the object. -or-…   More »

Use PSScriptAnalyzer in PowerShell Studio

Wednesday, May 11th, 2016 by June Blender
Applies to: Windows PowerShell 3.0 and later PSScriptAnalyzer 1.1.0 and later PowerShell Studio 5.2.118 and later PowerShell Studio has long supported best practices in Windows PowerShell, including running and debugging without profiles, avoiding cmdlet and parameter aliases (right-click\Expand to cmdlet, Expand all aliases: Ctrl+Shift+A), using consistent formatting to make maintenance and debugging easier, and using module-qualified command names (Ctrl+Shift+H). Beginning in PowerShell Studio 5.2.118, we've added deep support for PSScriptAnalyzer, the static analysis tool designed especially for Windows PowerShell. To use the Script Analyzer features in PowerShell Studio, you must be running in Windows PowerShell 3.0 and later and have…   More »

New Quick-Learn Video: Enclosures in PowerShell Studio

Monday, May 9th, 2016 by June Blender
We all love blog posts that explain something complex in simple terms or demonstrate an elegant technique for performing a task or solving a problem. But, sometimes, a quick video is more effective, especially when the result is visual. Also, there are many people who can learn more quickly by watching than reading. I've been spinning up some short videos about PowerShell solutions and cool features of SAPIEN products that are easy to miss in the treasure trove of features. They're all on our YouTube channel: YouTube.com/SAPIENTech. The latest video, Parentheses, Braces, Brackets & Quotes in PowerShell Studio, shows how…   More »

Setting Conditional Breakpoints

Wednesday, April 20th, 2016 by June Blender
Applies to PowerShell Studio 2016, PrimalScript 2016, and later. I write lots of scripts — for production, for research, for testing, and for demonstrations. And, inevitably, I hit a bug. I'm actually relieved when I do, because no code is perfect and I'd rather find the bugs before my users do. In fact, I make sure the content in my test database is full of oddities so it's as close to the real world as possible. When you are debugging with a large test sample, like a database or directory, the default line breakpoints are not sufficient. I can hit…   More »

Giving a talk? PowerShell Studio Presentation Features

Wednesday, March 30th, 2016 by June Blender
One of the best parts of the PowerShell community culture is the willingness of people at all levels of expertise to help others to learn. It acknowledges that we learn from each other all the time and pays backward and forward for help that others have given to us. So, there are many people giving talks and presentations about PowerShell. And, PowerShell Studio has several features that make presentations easier. Filegroups: Open all scripts and modules for your presentation in a single click, even if the code files are on different machines in different locations. The files open in PowerShell…   More »

PowerShell Studio 2016: Service Release v5.2.118 and PSScriptAnalyzer

Monday, March 28th, 2016 by David Corrales
We released a new service build for PowerShell Studio 2016 (v4.2.118). Here's what's new:   Support for PSScriptAnalyzer module PSScriptAnalyzer module is a community driven module that evaluates your PowerShell scripts and ensures they follow community approved best practices. http://www.powershellgallery.com/packages/PSScriptAnalyzer/   PowerShell Studio 2016 now allows you to run PSScriptAnalyzer directly from the ribbon (Tools->Analysis->Analyze Script): Note: This option will be disabled if the PSScriptAnalyzer is not installed.   When you use the Analyze Script command, the module results are displayed in the Debug Panel: Jump to the respective line in the script by double-clicking on result.   Triggered Analysis…   More »

Exporting from Modules: A Reminder

Thursday, March 24th, 2016 by June Blender
There are so many new things in Windows PowerShell that I often assume that I know the basics. But, while working on a project about modules, I ran into some new guidance from PowerShell developer Jason Shirk and a great blog post that demonstrates that information about variables in a TechNet topic about module manifests is wrong. Here are some important reminders about modules and their manifests: By default, all functions and aliases are exported, but variables are not exported. "By default, all variables are exported" in How to Write a Module Manifest (MSDN) is wrong. This topic is outdated…   More »

PowerShell Studio 2016: Custom PrimalSense

Tuesday, March 15th, 2016 by David Corrales
We've written a series of blog posts to introduce you to the newest features of PowerShell Studio 2016. In this blog, Part 4, we cover new customizable PrimalSense in PowerShell Studio 2016. But, there's more: In Part 1, we review the new UI features, including our new dark themes. In Part 2, we introduce our new debugging features, including variable and function breakpoints and improvements to the Variables pane. In Part 3, we look at some of the new editor features of PowerShell Studio 2016.   Custom PrimalSense Lists The new customizable PrimalSense feature allows users to tailor their PrimalSense…   More »