When I began the programming for http://www.sceptermarkeingtechnologies.com, I quickly noticed that Asp.net does not support the MessageBox class that I was familiar with in windows forms.

Since Asp.net runs on the server it doesn't have access to produce a modal dialog box on the client. However, by using a scripting language that runs in the clients browser a similar construct is available. In javascript the window.alert() function will produce a modal dialog similar to what you would expect from MessageBox in windows forms.

So, I decided to create a static class MessageBox with a static method Show(), which will give you the ablility to to still use the syntax MessageBox.Show("Your Message"); and then convert it into the javascript window.alert("Your Message"); and add the script to the end of the current response stream.

I've written a how to on my blog at: http://sceptermt.blogspot.com/2008/0...lass-in-c.html that shows the source code that I used in C# for my web application and details on how it works.

You could also write overloads for the static show() method to allow the class to do a javascript confirm() or a prompt(). I haven't needed that functionality yet so I've just kept it simple.

Check This out: http://www.sceptermarketingtechnologies.com

One comment about writing overloads for confirm or prompt is that this could be misleading from the perspective of the server code. The client side code runs only after the HTML is sent to to the browser. So any user response to a prompt or confirm dialog won't be seen at the server side but can only be consumed at the client side.

-Peter
peterlanoie.blog

You are right about the code being run on the client side and thus being the only forum for consuming the result from a confirm or prompt.

However, in an overloaded method javascript can be sent to the client that would cause the result of confirm or prompt to be posted back to the server where it can be handled on the server side.

It would be a quite complicated script but I was referring to the fact that it could be done.

Another approach to this problem is instead of using javascript you could use DHTML techniques to render the messagebox on the clients screen. That would allow the ok cancel or even yes no cancel buttons to be rendered as server controls as well as allowing the class to change the caption of the dialog or to style the whole thing to the design of your website.

Sorry if what I had said about overloading the send method being misleading, hope this post will clear things up.

Check This out: http://www.sceptermarketingtechnologies.com

No need to apologize. I've seen plenty of questions rooted in the misunderstanding of the separation of server-side and client-side code so I just wanted to clarify for the readers.

-Peter
peterlanoie.blog