I have just returned from the amazing lineup of PowerShell sessions at the NYC Techstravaganza. Sapien happened to sponsor the PowerShell track. This gave us the opportunity to hear what the company has been up to directly from their CEO, Dr. Ferdinand Rios. I should note, not only did we get updates about their 2012 products, but we were handed USB keychains that were fully loaded with beta software!
The session brought us through the updates that Sapien has made to iPowerShell, their iOS app and PrimalScript. Both had a whole set of new features, but it was the news about Primal Forms that I thought was worth blogging about. Here are some of the new features we saw (this is probably not a comprehensive list – it’s just the items that raised my eyebrow during the session):
Primal Forms is now called PowerShell Studio 2012
This makes a lot of sense to me. It is a name that more appropriately tells what Primal Forms is. It’s not only a full-fledged winform developing environment for PowerShell, but it’s also a fairly robust integrated scripting environment (ISE). The only downside is that there is already a codeplex project with this name. It’s sure to spin up some conflict or debate.
One thing is clear when working with Primal Forms 2011, you definitely don’t want/use all of the panes that you have open all the time. When working on forms, you need a whole different layout than you need when you want to just work on a simple script. Layouts can now be switched rapidly via a control in the bottom left. These layouts continue to happen automatically, but you can also control them manually.
Font Size Slider
This is a slider that will change the size of the fonts in your script window. I use this slider all the time in powershell_ise.exe when giving demos. I’m glad this simple change is now in the app.
This one is cool. There is a pane that will allow you to quickly click between events and functions in your projects. It’s dynamically built. Obviously, it’s really neat when trudging through the complex structure of a scripted winform, but I am finding that it’s really cool for large modules too.
There is an indicator between your code and the line numbers that are triggered during a change to your code. If you open a script, and then make a change to that script, a yellow indicator shows that this has been changed:
Once you save the file, the indicator turns green:
If you open the script again, the indicator resets to not being there.
Toggle a Cmdlet to and from an alias
Apparently, you could always toggle an entire script to remove all aliases. I was not aware of this. Regardless, you can now right click on a cmdlet or alias to toggle between the cmdlet and its aliases.
Cmdlets have a ‘Convert to Alias’ context menu:
Aliases have an ‘Expand to Cmdlet’ context menu.
I should note that as of the beta you can convert to the alias foreach or % in place of Foreach-Object, but you cannot expand it back to a cmdlet.
Tab Completion of .NET Methods
Neat-o feature. When you enter a method, you get a helper window to tell you the overloaded options. You can press up and down (or click up and down in the intellisense helper) to select the appropriate parameter set that you plan to use:
Once you have found the right method, you can press tab (like the helper says) to autofill the method’s parameters. This is really nice with classes that use an enumerator. It saves you from having to type out the entire class name. For example, the next image shows that it has typed the entire [System.MidpointRounding] for me.
It goes a bit further too. As you can see above, a variable name is created and highlighted. You can immediately start typing another variable or decimal. Once you are done entering that parameter, you hit tab to go to the next one. In the case of an enumerator, like the one above, it lets you select the item in the enumerator you would like to use. This is handled via another intellisense helper that you can quickly move to with the up and down arrows. It even gives you information about what the item does:
This is the one that matters! This is the promise of scripted GUIs in my opinion.
You can package sets of common form controls, events, and functions as a control set. This gives you an easy way to add something to your form that is a complete thing (for lack of a better word) via drag and drop. For example,
- You can add text boxes that have validation pre-configured so that it will validate whether or not you have an e-mail address or phone number.
- You can add charts that automatically pull data from a specific cmdlet.
- You can add buttons that run background processes or jobs that include status bars and indicators that help the end-user understand what is happening.
- You can also include a quick textbox that will automatically have a button with an associated file-dialogue box that will populate the textbox.
Here is a list of the control sets that are in the beta:
I should note that the “TextBox – Validate IP” is one that I created this morning during breakfast. I was floored by how easy it was to do (with some knowledge of winforms). Actually, not only easy, but they give you the ability to utilize shared controls between the control sets. In other words, if you already have an appropriate ErrorProvider object that can serve the validation for your TextBoxes, it will use that object rather than creating a new one if you tell the wizard that it can do so. I will be blogging a detailed tutorial on how to do this today or tomorrow.
Debugging a Script that uses Remoting
Okay, this is the final feature. The demo we saw did not show this. Also, the beta version we received does not yet have it. However, the promise was made in Ferdinand’s last slide. When PowerShell Studio 2012 ships sometime in the Spring, it will have a remote debugger.