Archive for the ‘PowerShell Studio’ Category


 

Why Breaking Changes?

Wednesday, November 23rd, 2016 by June Blender
In PowerShell Studio 5.3.130, we made some changes to projects that aren't recognized by previous versions of PowerShell Studio. This blog post describes the changes, explains why we made them, and offers a workaround in case you really need it. Also, note that SAPIEN has properly incremented the Minor property in the PowerShell Studio version number to 3 to indicate a breaking change. We went from 5.2.129 to 5.3.130. ----------------------- If you created a project in an older version of PowerShell Studio, PowerShell 5.3.130 and later will open and update your project. But, if you create or open a project…   More »

PowerShell Studio 2016 – Service Release v5.3.130

Tuesday, November 15th, 2016 by David Corrales
Today we release a new build of PowerShell Studio 2016 and it includes some major changes and new features.   Project Changes and Compatibility IMPORTANT: This build will convert your projects and create a backup of the original (*.psproj.bak). The new project version is not backwards compatible with older builds of PowerShell Studio. We made changed to our projects in order comply with the best practices and warning produces by PSScriptAnalyzer. Previously, when you invoke a GUI or script file from a project, you had to use a reference function that used a Call verb. For example: Call-MainForm_psf The Call…   More »

New Keyboard Shortcuts in PowerShell Studio 2016

Thursday, September 8th, 2016 by June Blender
The newest version of PowerShell Studio, 5.2.128, includes some nice updates, additions, and fixes, but I wanted to call your attention to the change in our keyboard shortcuts. We've updated them to simplify the most frequently used shortcuts and to make our shortcuts consistent with other Windows tools. Special thanks to our Wish List contributors for their suggestions. If you are using a keyboard shortcut program or you have a programmable keyboard or input device, you might need to adjust your settings. Find / Replace Ctrl + F or Ctrl + H Run Selection in Console F8 Run in Console…   More »

How Do Multi-Form Projects Work?

Thursday, July 28th, 2016 by June Blender
Applies to: PowerShell Studio 2016, Windows PowerShell 3.0+ I recently wrote an article with step-by-step instructions for creating a very simple multi-form PowerShell GUI application. In our sample app, we use PowerShell Studio features that make it very easy to open a child form from the main form and gets the text in the textbox on the child form. In this article, I'll explain what goes on in the background to make these features work. You might not care -- just so they work -- and that's fine. But if you're wondering how this happens, or you need to debug…   More »

Write a Multi-Form PowerShell GUI App

Tuesday, July 26th, 2016 by June Blender
Tested on: PowerShell 2.0+, PowerShell Studio 2016 This step-by-step example shows you how to create a very simple multi-form PowerShell GUI app. The app consists of a parent form that gets data from a child form and displays it. When you finish, you'll know how to use the basic multi-form features of PowerShell Studio. For details about how these features work under the covers, see How Do Multi-Form Projects Work? For this task, we assume that you know how to create a single-form PowerShell GUI app or that you've participated in a Thinking in Events hands-on lab. Otherwise, start with…   More »

PowerShell Studio 2016 – Service Release v5.2.125

Monday, July 25th, 2016 by David Corrales
We released a new service build of PowerShell Studio 2016 (v5.2.125)!   Here’s what’s new:   Blocked Files PowerShell Studio will now notify you when a script file is blocked. Windows flags files as blocked when downloaded from the internet or copied from a remote computer.   PowerShell Studio disables execution of blocked files for your security. When you wish to run the script, unblock the file using the file tab’s context menu:     Open with PrimalXML You can now open XML files directly in PrimalXML from the project panel using the context menu: You can also open help…   More »

PowerShell Studio 2016 – Service Release & High DPI Support

Tuesday, July 5th, 2016 by David Corrales
We released a new service build of PowerShell Studio 2016 (v5.2.124)!   Here’s what’s new: High DPI Support We have added high DPI support to PowerShell Studio’s UI. Those of you who previously ran PowerShell Studio on a high DPI monitor (Windows 10 in particular) probably noticed that the application appeared fuzzy. The fuzzy appearance is caused by Windows’ scaling of non-DPI aware applications. The good news is that this no longer the case with PowerShell Studio 2016. Not DPI Aware DPI Aware High DPI Layouts With high DPI screens, you will require high DPI layouts. When PowerShell Studio detects…   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 »