Very cool! Thanks!

Thus the credentials.  If you supply a mail server, port, and credentials...that's email...period   We use this everywhere.  The only thing that you cannot do is pull mail down from a POP3 server...but sending...no problem

Thanks Trent. I've heard that this can fail because ISPs block mail sent to servers outside of their domain. Is this something you've heard of? I.e. I'm accessing the internet via a wireless connection at a hotel or using the network connection at a client site, attempt to send an email via the SMTP server at my company and the hosting network blocks the email.

.NET actually has some good SMTP classes for sending emails.  Here is a simple example (I went ahead and showed how to authenticate as this is generally the next question.  If you are mailing from an internal server that will relay your message you might not need this, but I thought it would help.  Also, you can format the mail message to support HTML, etc.  I just showed you the basics.

Oh, how did you send the email? I've been thinking about doing this also, and am investigating ways of doing it.

Cool!



One thing to note is that I used the using statement. It closes the form when done (when the using code block is done). If you don't use this, then you should close the form after you are done with it. The form is still open otherwise.

Yup...I think we met the same conclusion at about the same time.  Here is what I did:

Set a public variable in the dialog form (Form2):

public String _userinfo;

On the cmdOK_Click event, I set the value of the comments textedit control to the public variable.

Then, on Form1, within the deep inner workings of the unhandled exception routine:

MyExceptionData mNewForm = new MyExceptionData(e.UnhandledException);
mNewForm.ShowDialog();
mUserData = mNewForm._userinfo;

I am passing the exception to the form because I am formatting the exception data on the form for my own (or other savvy users') review.

So far, so good...thanks a ton for your help!!
Bill

I'd open the form as a dialog (ShowDialog method), then access properties on the form to get the info from the form. Code would be something like this (my C# is a bit rusty...hopefully this gets the idea across):





Hope that helps!

#1 is solved by properly referencing the namespace.

That happens way too often for comfort . . . bah!  foiled again!

For the moment, the second need still eludes me. 

Curse you, Aqua-Scum!
Bill

Ok...I am now attempting to catch all unhandled exception in the program.cs.  What I want to do is popup a nice message telling the user that a bad thing has just happened and that the IT department has been sent an email.  This works.  The email gets delivered.  In addition to the nice message, I want to open a dialog window that will allow the user to enter any information that they would like to help explain what they were doing at the time of the error.  Once filled in, the dialog closes and adds that info to the body of the email before sending.

I am having two problems:

1)  The form that I created for doing this is not accessible by the code in program.cs.

2)  The string variable cannot be fed back to the program.cs routine.

Thought?
Bill