MessageBox and button options

I know this is going to sound like a very stupid question but I have never done this before.

I have a MessageBox that prompts the user if they want to continue if certain files exist. That part of the code is working. What I have never done before and what I don't know how to do is perform an action based on what button they choose on the message box. I don't what where that result is stored or how to call it.

Feel free to laugh at this question.

Jim

Nothing better than a free laugh :) !!!


If you type:

VB Code:

if msgbox("Continue ?",MsgBoxStyle.YesNo) =

Intellisense shows you a list of options....

VB Code:

if msgbox("Yes",MsgBoxStyle.YesNo) =  MsgBoxResult.OK Then
 'do this
else
 'do this
End if

Well not to be overly picky but:
if msgbox("Yes",MsgBoxStyle.YesNo) = MsgBoxResult.OK Then

This will never return MsgBoxResult.OK, since the box doesn't have an OK button. It'll return either MsgBoxResult.Yes or MsgBoxResult.No.

Lol... Yes very true.... but a few runs of the debugger he or I would of caught that... :)

Also, use MessageBox.Show() instead of msgbox :)

I aim to provide the entertainment value to this forum :D

What's the difference between using MessageBox.Show() and just msgbox()?

MsgBox is there just for backward compatibility. The .NET class that provides the same functionality is Messagebox.Show.

Ah I understand - if so then you should also probably use the MessageBoxButtons enum instead of MsgBoxStyle huh. I don't see an equivalent for MsgBoxResult?

edit: oh it's DialogResult.

Well that explains why I was getting a reference to the Microsoft.VB library....

Is that necessarily bad practice? It seems to me that using stuff in the VisualBasic namespace will work the same, it just makes references to classes that are VB-specific (so your resulting IL won't translate into other languages).

I don't think it is bad practice, but it will help if you use the framework classes instead of the VB namespaces if you can. The reason I say that is because the more familiar you are with the .net classes, the easier it is to actually convert code from other languages over to VB.Net.

I also think that the compatibility classes that you are calling, are actually wrappers that call the .Net Framework classes. So why would you want to add another layer in there when you can bypass it all together? I haven't verified this, but it seems to me that was all they did.

You're probably right (as was Pirate earlier when he pointed out something similar to me, I just didn't get it then).