{"id":14852,"date":"2018-04-30T06:00:57","date_gmt":"2018-04-30T13:00:57","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=14852"},"modified":"2018-04-27T13:32:47","modified_gmt":"2018-04-27T20:32:47","slug":"powershell-studio-working-with-azure-cloud-shell","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/04\/30\/powershell-studio-working-with-azure-cloud-shell\/","title":{"rendered":"PowerShell Studio: Working with Azure Cloud Shell"},"content":{"rendered":"

I have been playing around with my Linux environment and AzureRM.Netcore<\/strong> cmdlets for some time now. I have also been using my Windows 10 WSL (Windows Subsystem for Linux<\/em>) for working cross-platform with Microsoft Azure Cloud Shell.<\/p>\n

Azure Cloud Shell has been around for some time and has undergone some significant improvements\u2014notably the ability to pick which command line to use right from the browser.<\/p>\n

This image shows the Microsoft Azure Portal with the Azure Cloud Shell integrated into the browser:<\/p>\n

\"\"<\/a><\/p>\n

For more information check out Azure Cloud Shell documentation<\/a>.<\/p>\n

Be Creative<\/h3>\n

One thing I love about using PowerShell Studio by SAPIEN Technologies is the ability to be creative! The only limitation we put is on ourselves, so why not take it further with the Azure Cloud Shell?<\/p>\n

This is a good opportunity to take a moment and check out all of the Windows Controls that PowerShell Studio has available for building GUI forms:<\/p>\n

\"\"<\/a><\/p>\n

Let’s be creative and build a GUI form that uses the WebBrowser Control<\/strong> to host the Azure Cloud Shell.<\/p>\n

Build A Simple GUI<\/h3>\n

We can build a simple GUI and incorporate the WebBrowser<\/strong>\u00a0control with the following steps:<\/p>\n

Open a new empty form: File<\/strong> > New<\/strong> > New Form<\/strong> > Empty Form<\/strong>:<\/p>\n

\"\"<\/a><\/p>\n

When the form opens, in the Properties<\/strong>\u00a0panel change the Text<\/strong> property name from “Form”<\/em>\u00a0to “MyAzureCloudShell<\/em>“:<\/p>\n

\"\"<\/a><\/p>\n

From the Toolbox<\/strong>\u00a0panel > drag\/drop the WebBrowser<\/strong> control into the new form.<\/p>\n

If necessary, resize the form in the Forms Designer:<\/p>\n

\"\"<\/a><\/p>\n

To preview the form > on the Home<\/strong>\u00a0ribbon > select\u00a0Run<\/strong>.<\/p>\n

PowerShell Studio will prompt you to save the form > Enter an application name<\/strong>. It is also recommended to provide a folder name to create the executable:<\/p>\n

\"\"\u00a0<\/a>\"\"<\/a><\/p>\n

To complete the application we need to add the hypertext URL “http:\/\/shell.azure.com<\/em>” to the WebBrowser\u00a0<\/strong>control.<\/p>\n

Click on the form where the\u00a0webbrowser1<\/strong>\u00a0was added.<\/p>\n

In the Properties<\/strong>\u00a0panel > under the\u00a0Behavior<\/strong>\u00a0section > in the URL<\/strong> field > enter the value\u00a0“http:\/\/shell.azure.com<\/em>“:<\/p>\n

\"\"\u00a0<\/a>\"\"<\/a><\/p>\n

To preview the new application you will need to Sign In or Create an Azure account. A login message will be displayed when the application opens:<\/p>\n

\"\"<\/a><\/p>\n

Preparing Application Settings<\/h3>\n

Now, after successfully testing the\u00a0MyAzureCloudShell<\/strong> application, we are ready to create the executable.<\/p>\n

In PowerShell Studio, on the Deploy<\/strong> ribbon, in the Packager<\/strong>\u00a0section, select Settings<\/strong>:<\/p>\n

\"\"<\/a><\/p>\n

There are five\u00a0Script Packager<\/strong>\u00a0settings. We only need to configure the first four:<\/p>\n

\"\"<\/a><\/p>\n

Script Engine<\/strong> – Identify which script engine will be used to build the application.<\/p>\n

Select the Target<\/strong> as\u00a0“Microsoft Windows 64 bit<\/em>” and the Script Engines<\/strong>\u00a0as “SAPIEN PowerShell v5 Host (Windows)<\/em>“:<\/p>\n

\"\"<\/a><\/p>\n

Output Settings<\/strong> – In the Engine Settings<\/strong>\u00a0section, designate the Output file<\/strong>\u00a0name, and the Output folder<\/strong>\u00a0name where the executable will be created. The rest of the fields are optional:<\/p>\n

\"\"<\/a><\/p>\n

Execution Restrictions<\/strong> – In the\u00a0Operating Systems<\/strong> section,\u00a0select which Windows Operating Systems the application will execute (Window 7 – Windows 10):<\/p>\n

\"\"<\/a><\/p>\n

Version Information<\/strong> – Enter any application specific version information:<\/p>\n

\"\"<\/a><\/p>\n

After you have completed selecting all of the required application settings, click OK<\/strong>.\u00a0Now, it’s time to build the application executable.<\/p>\n

Build Application Executable<\/h3>\n

There are two options to create the executable:<\/p>\n

Build<\/strong>\u00a0– This option only builds the application executable.<\/p>\n

Build & Run<\/b> – This option builds the application executable and then executes the application.<\/p>\n

Select the\u00a0Build & Run<\/strong> option:<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

And, we are done!<\/p>\n

Recap<\/h3>\n

This article showed how easy it is to build a simple and practical Windows application with PowerShell Studio with only one Windows Forms Control.\u00a0 In this example we extended a browser-based tool to a Windows Application that can allow multiple executable instances when needed.<\/p>\n

\"\"<\/a><\/p>\n

Go ahead and try it out!<\/p>\n

Feedback<\/h3>\n

As always, if you have any ideas, comments, or feedback, please visit our feedback forum<\/a> and reference this post.<\/p>\n

 <\/p>\n

Max Trinidad is a Technology Evangelist at SAPIEN Technologies Inc., and a Microsoft PowerShell MVP. You can reach him at\u00a0maxt@sapien.com<\/a><\/em><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

I have been playing around with my Linux environment and AzureRM.Netcore cmdlets for some time now. I have also been using my Windows 10 WSL (Windows Subsystem for Linux) for working cross-platform with Microsoft Azure Cloud Shell. Azure Cloud Shell has been around for some time and has undergone some significant improvements\u2014notably the ability to […]<\/p>\n","protected":false},"author":47,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1115,1143,941,1238,703,1239],"tags":[41,1016,390,815],"class_list":["post-14852","post","type-post","status-publish","format-standard","hentry","category-bash","category-powershell","category-powershell-5-0","category-powershell-core","category-powershell-studio","category-pscore6","tag-gui","tag-powershell-studio","tag-web-browser","tag-windows-forms"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14852","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=14852"}],"version-history":[{"count":26,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14852\/revisions"}],"predecessor-version":[{"id":14952,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14852\/revisions\/14952"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=14852"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=14852"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=14852"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}