This project is read-only.


May 7, 2011 at 11:12 PM

Perhaps I migrate some of my extensions from the WPK version to the new Show-UI version.

May 8, 2011 at 12:29 AM

Agreed. I'd wait a bit. I know the authors of WPK and Boots are still discussing next steps in the merge.

May 14, 2011 at 5:57 PM

The current version is working.

The -OutputXaml from the WPK version can't be added now.

BTW, I always use ISE to start TryPowerShell.

I use Jaykul's sample file as tutorial. The samples using async crash the tool.

I hope we can tune it to run some more of the samples.


May 14, 2011 at 6:08 PM

Cool. I am not sure though what/when the final Show-UI will be. I will be waiting for that outcome. Then I will jump in.

Thanks for trying this out.

Jun 19, 2011 at 3:31 PM
Edited Jun 29, 2011 at 6:25 AM

Now we have got a Show-UI release.

It has a known issue, which will be fixed in the July revision. As I'm a great fan of the WPF 4.0 Datagrid, I need WPF 4.0.

There are some changes in menu binding. The old WPK code needs to be adapted. I spent some hours without succeeding on hope, that Jaykul provides a Show-UI version of his Menu example for his last PowerBoots version.

The most important problem is the menu binding. I have a current unpublished Show-UI version without the menu binding and without generation of GUI from XAML,

as in New-Window { "<Button Content='Hello World!' ></Button>"} -show

cf. those two Show-UIworkitems:,

Currently I'm waiting for the next release of Show-UI.

Jun 30, 2011 at 6:10 AM
Edited Jun 30, 2011 at 6:15 AM

Just published CS 67506. It is based on Show-UI 8f504e8ffd05 .

Menu Binding not working, I added 2 buttons as work around.

GUI by XAML, which worked in WPK not working, e.g.

New-Window { "<Button Content='Hello World!' ></Button>"} -show

Ideas for markup extensions:

  • Button to load tutorial
  • Something to show warnings and hints, perhaps just headers in different colours

Ideas for the application:

  • Editor for tutorial (just to have something to show Cut-Copy-Paste 
  • Move the link box into a menu
  • Copy Output to Input (I often use PowerShell to generate scripts)
  • I would like to include as many different WPF features as reasonable, somehow making it a periodic system of WPF