( Unless I'm reading it wrong, it describes the problem exactly, but the solution doesn't work. Remember to set to false the Causes Validation = false of the exit button Also you can put it in the mouse down even or Closing Form Event, any event that triggers before the validating event. IT is so annoying working with MS buggy implementation.
I took what you all had here and made some adjustments.
Working with instances of these classes allows the developer to provide robust error-handling solutions. NET Framework provides two general classes or exceptions that derive from the common An exception associated with the exception whose Inner Exception property you are accessing.
This is helpful when a series of exceptions are involved.
The Common Language Runtime (CLR) represents all errors as exceptions. The Framework class library (FCL) includes a large number of standard exception classes that encapsulate information about common errors.A network link to a server might fail just as you're transferring data.Or perhaps you simply didn't allow for a particular rare circumstance in your code. NET Framework offers a robust set of tools for dealing with these unexpected problems.In this chapter, we'll look at two facets of dealing with problems in . First, we'll demonstrate the programming that you can do to handle errors, allowing the user to make corrections when something goes wrong.Then, we'll demonstrate how you can use validation techniques to prevent bad data from being entered into your application in the first place.Each new exception can preserve the information about the previous one by storing it in this property.