HelpIf (GetAsyncKeyState && Label Forecolor)

You can't implicitly convert a short to a boolean... (well, in C++ you can).

If (GetAsyncKeyState(Keys.Down) And &H1) = &H1 AndAlso Label1.Forecolor = Color.Green Then

if((GetAsyncKeyState(VK_DOWN) & 1) == 1 && Label1->ForeColor == System:rawing::Color::Green)

If the function succeeds, the return value specifies whether the key was pressed since the last call to GetAsyncKeyState, and whether the key is currently up or down. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState. However, you should not rely on this last behavior; for more information, see the Remarks.

Remarks:
Although the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the pre-emptive multitasking nature of Windows, another application can call GetAsyncKeyState and receive the "recently pressed" bit instead of your application. The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon.

You can change the P/Invoke to a boolean.. always worked out for me
C#

Code:

[DllImport("user32.dll")]
static extern bool GetAsyncKeyState(System.Windows.Forms.Keys vKey);

VB

Code:

<DllImport("user32.dll")> _
Public Shared Function GetAsyncKeyState(ByVal vKey As System.Windows.Forms.Keys) As Boolean
End Function

And @Jason, correct if I'm wrong but doing an AND with 0x8000 will actually check if the key is down at the current moment. 0x1 checks if it was pressed since the last call to GetAsyncKeyState. Usually, the last option is better for loops cause the user might have pressed the key to, let's say, change the select option on a menu, when you're drawing the menu, so when you actually call GetAsyncKeyState the key is not down anymore, but it was down a few milliseconds ago.