{"id":6131,"date":"2008-05-22T02:16:00","date_gmt":"2008-05-22T02:16:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2008\/05\/22\/wpf-powershell-part-1-hello-world-welcome-to-the-week-of-wpf\/"},"modified":"2019-02-18T13:15:55","modified_gmt":"2019-02-18T20:15:55","slug":"wpf-powershell-part-1-hello-world-welcome-to-the-week-of-wpf","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/wpf-powershell-part-1-hello-world-welcome-to-the-week-of-wpf\/","title":{"rendered":"WPF & PowerShell – Part 1 ( Hello World & Welcome to the Week of WPF )"},"content":{"rendered":"

Welcome to the Week of WPF.  <\/span>During the next 7 days, I\u2019ll help show you how you can use WPF and PowerShell together.<\/font><\/p>\n

PowerShell could always script almost everything in .NET, but, prior to the recent CTP2 you could not script Windows Presentation Foundation (WPF) in PowerShell.<\/font><\/p>\n

Now you can script everything that WPF can do within PowerShell.<\/font><\/p>\n

This means you can write pretty sleek looking UIs in nice little PowerShell scripts.<\/font><\/p>\n

There are a lot of things you can do with this capability, but let\u2019s start things off simple.<\/font><\/p>\n

 <\/font><\/p>\n

Windows Presentation Foundation (WPF) is a set of .NET libraries for making next-generation user interfaces.  <\/span>In order to script WPF classes, you have to start them in a Single Threaded Apartment (STA).  <\/span>Luckily, starting in CTP2, you can run code in an STA a few ways in PowerShell.<\/font><\/p>\n

 <\/font><\/p>\n

In order to script WPF, you have to do one of three things:<\/font><\/p>\n

\u00b7<\/font>         <\/span><\/span><\/span>Run the Script in Graphical PowerShell, where WPF scripts will run without any changes because Graphical PowerShell runspaces are STA.<\/font><\/p>\n

\u00b7<\/font>         <\/span><\/span><\/span>Run the script in PowerShell.exe and add the \u2013STA script<\/font><\/p>\n

\u00b7<\/font>         <\/span><\/span><\/span>Create a background runspace that is STA, and run the script in the background runspace<\/font><\/p>\n

 <\/font><\/p>\n

In this post, I\u2019ll show you a \u201cHello World\u201d script, and how to run it in each of the three modes.<\/font><\/p>\n

 <\/font><\/p>\n

First, let\u2019s write our \u201cHello World\u201d script.   <\/span>Open up Graphical PowerShell (gPowerShell.exe) and create a new script file (CTRL + N).<\/font><\/p>\n

 <\/font><\/p>\n

Here\u2019s the Hello World file:<\/font><\/p>\n

 <\/font><\/p>\n

$window = New-Object Windows.Window<\/span><\/p>\n

$window.Title = $window.Content = \u201cHello World.  Check out PowerShell and WPF Together.\u201d<\/span><\/p>\n

$window.SizeToContent = \u201cWidthAndHeight\u201d<\/span><\/p>\n

$null = $window.ShowDialog()<\/span><\/p>\n

 <\/font><\/p>\n

Now in Graphical PowerShell, you should be able to just run it and be done.<\/font><\/p>\n

 <\/font><\/p>\n

You can run the current script in Graphical PowerShell with F5 or the Green Run button in the upper left of the editor.<\/font><\/p>\n

 <\/font><\/p>\n

Now let\u2019s run the script in STA Mode PowerShell (Run PowerShell \u2013sta).  <\/span>Save it as \u201cHelloWorld.ps1\u201d<\/font><\/p>\n

 <\/font><\/p>\n

Since PowerShell.exe \u2013sta doesn\u2019t load up WPF\u2019s assemblies, lets run these three lines to add the references:<\/font><\/p>\n

 <\/font><\/p>\n

Add-Type \u2013assemblyName PresentationFramework<\/span><\/p>\n

Add-Type \u2013assemblyName PresentationCore<\/span><\/p>\n

Add-Type \u2013assemblyName WindowsBase<\/span><\/p>\n

.\\HelloWorld.ps1<\/span><\/p>\n

 <\/font><\/p>\n

Now you have a Hello World in WPF from the console version of PowerShell.<\/font><\/p>\n

 <\/font><\/p>\n

Finally, you can embed scripts to generate WPF inside of an application or a background runspace.  <\/span>This has some advantages over the first two approaches\u2026 namely, without a background <\/font><\/p>\n

 <\/font><\/p>\n

The code below will create a background runspace and set the two properties required to make WPF work in a PowerShell runspace, ApartmentState and ThreadOptions.  <\/span>ApartmentState determines if the runspace PowerShell is single or multithreaded (WPF requires single threaded), and if the same thread is used every time a command is run, or if a new thread is created each time.  <\/span>For WPF scripting to work in a runspace, you have to set ApartmentState to \u201cSTA\u201d and ThreadOptions to \u201cReuseThread\u201d.  <\/span>In the code below, the first 3 lines set up the runspace, the next 10 lines ensure that runspace is able to load WPF classes, and the final 4 lines run our original HelloWorld.ps1<\/font><\/p>\n

 <\/font><\/p>\n

# Create a runspace to run Hello World<\/span><\/p>\n

$rs = [Management.Automation.Runspaces.RunspaceFactory]::CreateRunspace()<\/span><\/p>\n

$rs.ApartmentState, $rs.ThreadOptions = \u201cSTA\u201d, \u201cReuseThread\u201d<\/span><\/p>\n

$rs.Open()<\/span><\/p>\n

# Reference the WPF assemblies<\/span><\/p>\n

$psCmd = {Add-Type}.GetPowerShell()<\/span><\/p>\n

$psCmd.SetRunspace($rs)<\/span><\/p>\n

$psCmd.AddParameter(“AssemblyName”, “PresentationCore”).Invoke()<\/span><\/p>\n

$psCmd.Command.Clear()<\/span><\/p>\n

$psCmd = $psCmd.AddCommand(“Add-Type”)<\/span><\/p>\n

$psCmd.AddParameter(“AssemblyName”, “PresentationFramework”).Invoke()<\/span><\/p>\n

$psCmd.Command.Clear()<\/span><\/p>\n

$psCmd = $psCmd.AddCommand(“Add-Type”)<\/span><\/p>\n

$psCmd.AddParameter(“AssemblyName”, “WindowsBase”).Invoke()<\/span><\/p>\n

$sb = $executionContext.InvokeCommand.NewScriptBlock(<\/span><\/p>\n

(Join-Path $pwd “HelloWorld.ps1”)<\/span><\/p>\n

)<\/span><\/p>\n

$psCmd = $sb.GetPowerShell()<\/span><\/p>\n

$psCmd.SetRunspace($rs)<\/span><\/p>\n

$null = $psCmd.BeginInvoke()<\/span><\/p>\n

 <\/font><\/p>\n

This is just a taste of some of the fun that PowerShell and WPF can have together, and how to get it working.  <\/span>You can now use everything in WPF in a PowerShell script.<\/font><\/p>\n

 <\/font><\/p>\n

During the Week of WPF, I will post one script each day that will take us a little further down the rabbit hole of what PowerShell and WPF can do together.  <\/span>After the week of WPF is done, keep your eyes on this space, because every Wednesday, I\u2019ll try to post a \u201cWPF Wednesday Widget\u201d that uses showcase using PowerShell and WPF together.<\/font><\/p>\n

 <\/font><\/p>\n

Hope this Helps,<\/font><\/p>\n

James Brundage [MSFT]<\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

Welcome to the Week of WPF.  During the next 7 days, I\u2019ll help show you how you can use WPF and PowerShell together. PowerShell could always script almost everything in .NET, but, prior to the recent CTP2 you could not script Windows Presentation Foundation (WPF) in PowerShell. Now you can script everything that WPF can […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[96,248,295,322,360],"class_list":["post-6131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-add-type","tag-powershell","tag-runspace","tag-sta","tag-wpf"],"acf":[],"blog_post_summary":"

Welcome to the Week of WPF.  During the next 7 days, I\u2019ll help show you how you can use WPF and PowerShell together. PowerShell could always script almost everything in .NET, but, prior to the recent CTP2 you could not script Windows Presentation Foundation (WPF) in PowerShell. Now you can script everything that WPF can […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/6131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=6131"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/6131\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=6131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=6131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=6131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}