Skip to main content

Getting information back from a Message Box with PowerShell

Sometimes I want a script to run automatically, but still prompt me before it takes an action.  A neat way of doing this is with a pop up message box.  Utilizing the MessageBox class from the .NET Framework, we can do just that.  For example, maybe I have a script that notifies me with the Dow Jones Industrial Average drops by 300 points in the current trading session.  Hey, that is a money making opportunity! 
1
2



3
4
5
6
[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
$Answer = [Windows.Forms.MessageBox]::Show("DJIA has dropped by 300 points today `n Do you want to `n go to your IRA?", "Trade Alert",
          [Windows.Forms.MessageBoxButtons]::YESNO,
          [Windows.Forms.MessageBoxIcon]::Information)

If ($Answer -eq "Yes")
{
    Write-Host "Do Something."
}
Essentially, line 1 gives us access to the Windows Forms objects.
Line 2 Saves the answer of our message box in a the variable $Answer.  To control the type of message box that we display, we have several options. 

The Windows.Forms.MessageBox class is overloaded.  That means that you can implement it in several different ways.  In this instance, we are using the Show method.  Take a look at the screen shot below of the many different versions of the Show method for this class:
image
What differentiates each call to the MessageBox class is the number of arguments and their data types that you pass to the class.  In this case, we passing the 7th item which is String, String, MessageBoxButtons, MessageBoxIcon.
Clicking on this item, we are taken to the MessageBox.Show Method (String, String, MessageBoxButtons, MessageBoxIcon) method on MSDN.  Here we can see that the first string is the message and the second is the caption on the message box window.
image
From here, if we click on System.Windows.Forms.MessageBoxButtons, we can see the types of buttons that we have access to.
image
In this example, we are using YesNo. Yes or No will be returned and stored in $Answer
We are also choosing an icon for this message box from MessageBoxIcon. Here are valid options are:
image
In the end, this is what you will see:
image
Either the string Yes or No will be returned when the appropriate button is clicked.

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.