I feel I should point out that because of the way this module is written, there is essentially no help available for the various commands (mostly because those commands don’t really exist, they’re all just aliases to the same New-WpfElement function).
In order to make up for this as much as possible, I have provided at Get-BootsHelp function which takes an element name (eg: Window, Button, etc) and opens the MSDN documentation for that type, which includes links to all the information about the properties and events represented by the PowerBoots parameters.
To get a complete list of PowerBoots elements, you can run Get-BootsCommand, but be aware that the elements are generated dynamically from the *.Proxies.txt files in the module folder, so you can easily add your own either following the naming convention for the files (Module^Namespace.Proxies.txt), and listing the types you want proxied inside, or by calling Add-BootsFunction with another assembly or specific classes.
This is my favorite release of PowerBoots so far, even though for the first time I am breaking backwards compatibility with your existing scripts. I’m sorry about that, but I promise it’s for the best, and will result in better performance and features in the future, as well as causing less confusion going forward — because it means new support for PowerShell 1.0 for the main cmdlets (and all the new features in this release support v1) with support in other areas coming soon…
To show you just how cool this can get, I’ve included a single theme from the codeplex wpfthemes project called DavesGlossy. I removed a few things so it’s not as slick as the one on CodePlex, but it doesn’t depend on WPFToolkit
This is by far not the last release of this module. I’ve kept the version number low primarily because I’m pretty sure that I will still need to make some significant changes. I have an idea to make the full ‘boots syntax work on PowerShell 1.0, and to clean up the syntax for animations, events, and attached properties. Once I get it working in v1.0 we should even be able to make it have proper help functionality.
PowerBoots is a .Net GUI framework. As such, it requires Single Threaded Apartment mode, as opposed to the Multi-Threaded Apartment mode that PowerShell defaults too. In these older script-only versions, you have to start PowerShell with the -STA switch for it to work. There aren’t really any noticeable downsides to running PowerShell this way, so my current recommendation is that you simply edit your PowerShell shortcut and append a -STA to the end of the command line. For a discussion of the differences, see the MSDN page on processes, threads, and apartments.
The first public release of the PowerBoots script module for PowerShell 2 CTP3.