sapien powershell studio using input b oxes

In this case, I have the dialog box to display the desktop.Īt this point, the dialog box will not display. This tells the OpenFileDialog class which folder to display when the dialog box comes up. You can see above that the OpenFileDialog class constructor has an InitialDirectory argument.

$FileBrowser = New-Object -Property InitialDirectory = ::GetFolderPath('Desktop') } Once we've loaded the assembly, we can instantiate an OpenFileDialog object using New-Object. NET assemblies are typically loaded for you, but in this case, we have to do it manually. To do this, we'll first need to load the assembly manually using the Add-Type cmdlet. NET class we need, which means we can also bring up the open file dialog box. Did you know you can get input to your PowerShell scripts this way too? Since PowerShell lies directly on top of. NET assembly called with a class inside called OpenFileDialog. The software you're using to invoke this dialog box uses a. This has greatly helped my colleagues know exactly what to run and how.įeel free to check it out for yourself at my site: dialog box is standard across lots of Windows applications.

By doing this, I took the guess work out of determining which PowerShell script to run for a given task. I decided to standardize and consolidate all of those scripts into one menu driven PowerShell GUI. Before I created the menu driven PowerShell GUI, I had directories and directories of very specific scripts to do specific tasks.

I really enjoy automating manual administrative tasks, so that is what drove this project in the first place. I wanted something that was very powerful yet very simple to maintain. I finally decided a few years ago to create a very simple menu driven PowerShell GUI. Over the years, I have supported and created multiple types of GUIs.

Sapien powershell studio using input b oxes