24

This might be a pretty simple question but I'm totally lost and searching for an answer hasn't been helpful.

I've got some powershell code to display a simple GUI with TextBoxes. Some of the textboxes allows the user to press Enter to run Button_Click code. When I try running the PS1 script, I get errors saying the following:

Unable to find type [System.Windows.Forms.KeyEventHandler].
Make sure that the assembly that contains this type is loaded.At C:\Scripts\GUI-Testing.ps1:161 char:1

$TestVar=[System.Windows.Forms.KeyEventHandler]
CategoryInfo          : InvalidOperation: (System.Windows.Forms.KeyEventHandler:TypeName)
FullyQualifiedErrorId : TypeNotFound

The strange part, if I close the GUI then re-run the script, I don't get the Unable to find type error and pressing Enter works as desired.

Thinking I had an answer, I tried using [void][reflection.assembly]::Load('System.Windows.Forms.KeyEventHandler') which give this error Exception calling "Load" with "1" argument(s): "Could not load file or assembly 'System.Windows.Forms.KeyEventHandler' or one of its dependencies. [FileNotFoundException]

user4317867
  • 2,397
  • 4
  • 31
  • 57
  • I should be loading this already with `[void][reflection.assembly]::Load('System.Windows.Forms, Version=2.0.0.0, Culture=neutral')` – user4317867 Jan 06 '15 at 04:37

2 Answers2

37

Make sure you load the following assemblies at the top of your script:

[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Drawing") 
[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")

If it's still not working, you could do something like:

$objForm.KeyPreview = $True
$objForm.Add_KeyDown({
    if ($_.KeyCode -eq "Enter") 
    {    
        #Write Code Here
    }
})
Frédéric Bégin
  • 601
  • 6
  • 7
  • 1
    Thanks, I was going off other examples and the assemblies were being loaded under the Enter key press variables. Makes sense powershell would complain about things. Now powershell is happy! Thanks! – user4317867 Jan 06 '15 at 05:00
  • 2
    why not add-type -AssemblyName "System.Windows.Forms" ? – DOSLuke Jul 28 '21 at 13:23
  • 1
    Neither `add-type ....` nor `[System.Reflection.Assembly]::LoadWithPartialName(...)` have any effect. Both execute w/o errors, but the `Forms` assembly/module is just not getting loaded.. Any hints? – huoneusto Sep 02 '22 at 10:50
  • 1
    @huoneusto that has been deprecated, see https://learn.microsoft.com/en-us/dotnet/api/system.reflection.assembly.loadwithpartialname?view=net-6.0 The overloads of the Assembly.LoadWithPartialName method are obsolete and have been retained for backward compatibility. The non-obsolete alternative is Assembly.Load(String). – user4317867 Sep 15 '22 at 05:19
0

This code opens Notepad and types "Hello"

[void][System.Reflection.Assembly]::LoadWithPartialName("System.Drawing") 
[void][System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") 

add-type -AssemblyName microsoft.VisualBasic
add-type -AssemblyName System.Windows.Forms

Start-Process -FilePath "notepad.exe"
start-sleep -Milliseconds 500

[Microsoft.VisualBasic.Interaction]::AppActivate("Notepad")
start-sleep -Milliseconds 100
[System.Windows.Forms.SendKeys]::SendWait("+{h}")
start-sleep -Milliseconds 100
[System.Windows.Forms.SendKeys]::SendWait("{e}")
start-sleep -Milliseconds 100
[System.Windows.Forms.SendKeys]::SendWait("{l}")
start-sleep -Milliseconds 100
[System.Windows.Forms.SendKeys]::SendWait("{l}")
start-sleep -Milliseconds 100
[System.Windows.Forms.SendKeys]::SendWait("{o}")
start-sleep -Milliseconds 100

Here is another example below that doesn't show anything but instead sends keystroke "ctrl+schift+alt+a":

[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Drawing") 
[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") 

add-type -AssemblyName microsoft.VisualBasic

start-sleep -Milliseconds 2500

[System.Windows.Forms.SendKeys]::SendWait("(^+%{a})")
Sgt.Foose
  • 23
  • 8
  • Simple script to run from the PowerShell CLI. Just open Powershell, browse to the directory of the script using "cd", type the name of your script (e.g. test1.ps1) and hit enter. Please note, sometimes you need to add the "Path" of the folder to your Windows System Environment Variables by typing "Path" in the Windows Search bar. – Sgt.Foose Dec 01 '22 at 09:20