In lines 55-63 we check to see if the module we just added is included in our installed modules ($instModules) array and if it is, we add a checkmark image to the list control. See this article for more detailed information about the TAG property.
We also store the module itself in the listItems’s TAG property for easy access to the module later. For each module in $psgModules, we get the name and the version and place those items into the list control. EndUpdate calls, we delay drawing the list until all the work has been done, thereby eliminating flashing of the list control. Then in line 43 we use Get-InstalledModule to get a list of the currently installed modules and store that as well ($instModules). Using the Find-Module cmdlet (line 40), we connect to the PSGallery and store the result in a local variable, $psgModules. In lines 31-34, we check to see if there is an item selected, and if so, we store that item’s index. In lines 24-29, we store the top item’s index so that when we refresh the list we can return it to the same position.
#Alternative to sapien powershell studio code#
We also could have put this code in a separate thread so as not to impact the UI. This is a fairly long function so let’s go through it a step at a time.įirst, because we know that this function will take a bit of time (as it needs to communicate across the internet), we change the cursor to a wait cursor on line 22. Bear in mind that many object properties have been manipulated in the object ‘s Property list to help create a working UI. So for a BUTTON named MyButton, the CLICK event handler would be named:įor the purposes of this blog article, we are only going to examine the actual code that gets executed when an event occurs. Event handlers are named using the following formula: Default event handlers are automatically generated by PowerShell Studio when you double-click on an object in the designer. For instance, when a user clicks on a button, that button’s “click” event handler is called. These are functions that are called by the application when a specific event occurs. Since GUI applications are event driven, most of our operational code goes into event-handlers. (Actually, these are inserted automatically by PowerShell Studio when we include the appropriate cmdlet in our code.) The bottom pane is basically a dump of all the actions that are taken by the user and PowerShell cmdlet responses.Īt the top of our file we start off with two calls to Import-Module: the first to import PowerShellGet and the second to import PackageManagement. The top right pane shows details for the module selected from the module list. The top left pane displays a sorted list of the modules found on the PowerShell Gallery. PS1 file and “modularized” it and posted it to the PowerShell Gallery here.įigure 1 shows the completed application interface. PS1 file that can be run from the PowerShell console. For those without PowerShell Studio, we have exported the complete project into a. The github repository contains the complete PowerShell Studio source code as well as a packaged. The complete source code can be found on the SAPIEN github repository here. The application creates an interface that displays gallery module information and allows the user to easily add and remove modules from their system. The recorded talk should be available at some point on the PowerShell Conference Asia Website. Finishing work was done by Devin Leaman of SAPIEN Technologies.
During that talk, I developed an application that used PowerShell’s PSGet module to communicate with the PowerShell Gallery.
The talk centered around GUI application design and development using PowerShell as the core language. Back in mid-September, I presented a talk on “Building PowerShell GUI Tool Solutions” at the PowerShell Conference Asia in Singapore.
0 kommentar(er)
