Hi Mike,
Well, the benefit of the messaging component is two-fold:
1) If you're localizing you're messages, you can use the localization editor to create the message in several different languages and let the runtime figure out which language to show when it shows the messages.
2) Whether you're using localization or not (and if I remember correctly, you probably won't be localizing), using the messaging interface allows you to remove embedded text from your application. This gives you the following benefits:
a) You don't have to be a developer to change a message because of a type-o
b) You can reuse messages by reusing the key, rather than copying the text multiple places within your application
c) You can associate an event ID with each message, then when one of your users calls you and says, "Hey, I just got message #157," you know exactly which message they're talking about.
d) You have a central location for managing messages, allowing you to change a message in one place rather than trying to do a "Find and Replace All" in your code
There are other benefits as well, such as the MessageForm being much prettier than the standard .NET MessageBox and the ability to use RTF formatting in your messages.
Hope that helps
