You probably know them already, but if you’re new to Win32, here are some key window messages. I would normally suggest that you commit them to memory, but if you do enough debugging, you’ll end up memorizing them anyway because you see them all the time.

I include 0x001A in the list even though it is a low-traffic message because you do see it a lot when you are investigating hangs. The WM_SETTINGCHANGE (which also goes by the name WM_WININICHANGE) is a common culprit when investigating why your program has wedged: You’re broadcasting a notification and there’s a window in the system that isn’t responding.

I know that Visual Studio has a shortcut for decoding error codes. I wonder if it has one for decoding message numbers.