The headline for this submission could definitely use some improvements.
The headline “Visual Studio commands” suggests an article containing such nuggets of wisdom as “You can press F5 to compile and run your program”. It fails to communicate what the article is actually about.
Good high level overview, but the above quoted section is incorrect. IMenuCommandService is not a global service, in fact it is somewhat of a faux service as it is available only inside MPF derived types (WindowPane and Package) and each derived type gets its own, isolated instance. It is not how VS itself "does" commands, but rather bus convienence introduced by MPF. You can also assign handlers for commands defined by others (or the shell) in the same way, but package level handlers will only be invoked for the package that defined them.
This article deals with creation, utilization and handling of Visual Studio commands in its extension modules through automation object model APIs and IDE services. The relations between IDE commands and environment UI elements, such as user menus and toolbars, will also be examined.