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. Visual Basic
  4. VB.NET ApplicationContext Unhandled Exceptions

VB.NET ApplicationContext Unhandled Exceptions

Scheduled Pinned Locked Moved Visual Basic
csharpdatabasesysadmindebugging
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.
  • M Offline
    M Offline
    Moonark
    wrote on last edited by
    #1

    I am working on a few applications in VB.net which use a custom application context for many things such as showing the splash screen, database login form, and finally launching the main form. I have looked all over for a way to put a unhandled exception handler in the custom Application Context so anything that "spawned" from it so to speak would be covered if a exception occured. Is there a way that this can be done? I have tried a few of the examples on CodeProject but still no luck. Doing something like Throw New Exception("this is a test") without a Try Catch will cause the debugger to popup and not the exception handler. Thanks in advance... The network is down...let's go get bagels.

    D 1 Reply Last reply
    0
    • M Moonark

      I am working on a few applications in VB.net which use a custom application context for many things such as showing the splash screen, database login form, and finally launching the main form. I have looked all over for a way to put a unhandled exception handler in the custom Application Context so anything that "spawned" from it so to speak would be covered if a exception occured. Is there a way that this can be done? I have tried a few of the examples on CodeProject but still no luck. Doing something like Throw New Exception("this is a test") without a Try Catch will cause the debugger to popup and not the exception handler. Thanks in advance... The network is down...let's go get bagels.

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      What do you mean by "custom Application Context"? Are you talking about AppDomains? Exceptions will not cross AppDomain boundries. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      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