Global (system-wide) hotkey with Powershell

Question

 
Hi, i have a winform which is minimized/or hidden and would like to make it appear with a global (system wide) hotkey. (see bogus "new-hotkey"-cmdlet below)
[void][System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
$form1 = New-Object 'System.Windows.Forms.Form'
$form1.ClientSize = '300, 250'
$form1.windowstate = "minimized"
# -- bogus(!) code --
$hk = new-hotkey -scope Global -keys "Ctrl,Shift,Z" -action ({$form1.windowstate = "normal" })
$form1.ShowDialog()
I searched the web intensively but only found C# solutions, which i could not translate into powershell (v3). I tried but it did not work:
http://stackoverflow.com/questions/23855928/acessing-c-sharp-code-in-powershell
The trouble is: even if i manage to use some C# code in my script, because i do not understand C#, i can't debug it.
I tried a few third-party tools, like WASP, Pseventing, Autohotkey, but they all have disadvantages or did not work correctly, so using C# in Powershell is seemingly the way to go.
I'm sorry, cause i know its not appreciated, but i need a working solution, not just tips how the get started.
thanks a lot, Rob

Answer 1

http://www.fluxbytes.com/csharp/how-to-register-a-global-hotkey-for-your-application-in-c/ shows the basics of how to accomplish this, by using the Win32
API RegisterHotKey function (which you've already found, by the looks of your StackOverflow post.)  Converting this to run PowerShell code in response to the hotkey might be a bit complicated, and also unnecessary in your case (since you seem to just
want to change the value of a property on the form, you could do that right in the C# WndProc method, or whatever it calls in response to your hotkey.
To make something more generic which can cause PowerShell code to execute, I'd probably have the form raise an event in response to the Windows message.  Then PowerShell scripts can use Register-ObjectEvent to respond to it, and you don't have to worry
about problems with threads or runspaces (since the PowerShell engine already takes care of that for you when you use Register-ObjectEvent.)