Crouchie,
Although I use forever Messagebox, is your statement not true,
MsgBox versus MessageBox.Show
In Visual Basic .NET, the MsgBox method is a Visual Basic Runtime wrapper
around a call to the MessageBox.Show method from the System.Windows.Forms
namespace. MsgBox does some extra work to emulate the behavior of the Visual
Basic 6 MsgBox function before culminating in a call to MessageBox.Show. The
minute cost of these emulating steps is insignificant, particularly when
compared to the time it takes a user to react to a dialog box.
Note MsgBox returns the same integer values returned by MessageBox.Show.
Strictly speaking MessageBox.Show returns a DialogResult value and MsgBox
returns a MsgBoxResult value. The values in these enumerations have the same
meanings: OK = 1, Yes = 6, No = 7, and so on. You can also use CType to
convert a MsgBoxResult to a DialogResult.
The choice between MsgBox and MessageBox is a matter of consistency. If you
are migrating a Visual Basic 6 application to Visual Basic .NET, there is no
compelling reason to replace calls to MsgBox with MessageBox.Show.
Recommendation: Use MsgBox throughout your code.
From this page
http://msdn.microsoft.com/library/d...tml/vbtchmicrosoftvisualbasicnetinternals.asp
However I have as well the idea that there are more and more a lot of
*recommendations* on MSDN which conflict with each other.
Cor