Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Message pump exception catching

Message pump exception catching

Scheduled Pinned Locked Moved C#
questionwinformstutorial
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    Hugo Hallman
    wrote on last edited by
    #1

    Hey all. I suppose this is easy really, but I don't know how to do it. How can I catch exceptions that occur in message handlers i windows forms? It's also gotta be before the default message pump exception handler. I have some exceptions that can occur at a million places on user input, and should be handled centrally. Thanks in advance.

    H 1 Reply Last reply
    0
    • H Hugo Hallman

      Hey all. I suppose this is easy really, but I don't know how to do it. How can I catch exceptions that occur in message handlers i windows forms? It's also gotta be before the default message pump exception handler. I have some exceptions that can occur at a million places on user input, and should be handled centrally. Thanks in advance.

      H Offline
      H Offline
      Heath Stewart
      wrote on last edited by
      #2

      Honestly, there's no reason an exception should be thrown to the message pump. Following the doctrine of "never trusting user input", all input should be validated prior to doing anything with it. In any case, Application.ThreadException should typically do the trick. Even the event documentations states about what I said above, though. Always validate user input as close to the input as possible (i.e., the presentation layer or in methods and property set accessors that can be called by outside code).

      Microsoft MVP, Visual C# My Articles

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups