You can add an event handler to AppDomain.UnhandledException event, and it’ll be called when a exception is thrown and not caught.
More Related Contents:
- Is there a difference between “throw” and “throw ex”?
- WPF global exception handler [duplicate]
- Best practices for catching and re-throwing .NET exceptions
- .NET Global exception handler in console application
- .NET – What’s the best way to implement a “catch all exceptions handler”
- Will code in a Finally statement fire if I return a value in a Try block?
- What’s the difference between Application.ThreadException and AppDomain.CurrentDomain.UnhandledException?
- Handling exceptions, is this a good way?
- The calling thread cannot access this object because a different thread owns it [duplicate]
- How can I catch a 404?
- Why is try {…} finally {…} good; try {…} catch{} bad?
- When to use try/catch blocks?
- How to check if IOException is Not-Enough-Disk-Space-Exception type?
- Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
- What is ApplicationException for in .NET?
- Show line number in exception handling
- What really happens in a try { return x; } finally { x = null; } statement?
- How to log all thrown exceptions?
- Why does the order of alternatives matter in regex?
- When should I use Lazy?
- Does .NET FtpWebRequest Support both Implicit (FTPS) and explicit (FTPES)?
- Windows Forms Graphic Issue on Windows 10 OS
- Step by step tutorial to use SAP. net Connector with VS 2008 [closed]
- Get timestamp from Authenticode Signed files in .NET
- CryptographicException was unhandled: System cannot find the specified file
- How to serialize an Exception object in C#?
- Looking for a Command Line Argument Parser for .NET [closed]
- The extern alias ‘xxx’ was not specified in a /reference option
- ThreadStaticAttribute in ASP.NET
- What is the “base class” for numeric value types?