What to do when an unexpected exception occurs?
Sometimes the right move is to let it throw (no catch at all).
Other times, it’s better to catch it, log it, and continue.
This decision isn’t clearly shared anywhere, so I created my own best decision table.
For C#/.NET Windows app & service developers, I organized it practically around failure containment, state pollution, and explainability of external side effects.
It’s the eternal theme for engineers building long-running apps and services.
Use this table as a reference for restart-first safe design!
comcomponent.com/en/blog/202…#CSharp#dotnet#ExceptionHandling#WindowsAppDevelopment