Off the top of my head: * 'The file "filename" already exists.' is sufficient for your users when you try use FileMode.CreateNew? I would want to ask the user if they wish to overwrite so they don't have to open Windows Explorer and delete the file. * 'Access to path "filename" is denied' is sufficient for your users for *both* files marked as read-only and files they don't have access to via ACL. The user can do something if the read-only bit is set; they can't if their Admin has denied them access via ACL. * ex.Message is not localized. If I bought a Spanish version of the software running in English Windows, I still want to see Spanish messages. * ArgumentNullException, ArgumentOutOfRangeException: these would provide useful messages. * A "Retry" button would be nice with file access attempts. It would be hard to decide whether "Retry" is an option without knowing more detail about the exception. "Retry" on FileNotFoundException, DirectoryNotFoundException, PathTooLongException, or ArgumentException just doesn't make sense.
http://www.peterRitchie.com/ On Mon, 19 Sep 2005 09:57:44 -0400, Eames, Andrew <[EMAIL PROTECTED]> wrote: >You put up a MessageBox showing ex.Message - in response to the user >typing in a filename that you can't open >In fact this is a good case in point where you will be more robust to >the CLR adding a new exception, not less > Andrew =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
