I should have elaborated, but basically what MD87 replied. During the development of .NET it was decided that every exception caused by programs should inherit from ApplicationException, and all system errors should inherit from SystemException. Unfortunately .NET devs didn’t follow this and now everything should just inherit Exception since it’s easier to check. Interestingly, both SystemException and ApplicationException seem functionally identical to Exception.
It is a relic of the past, where Microsoft intended developers to inherit all their custom exceptions from ApplicationException. Shortly after, they changed their mind and advised that custom exceptions should derive from the base Exception class.
M$ Docu sounds like that doesn’t make sense, do you have some more context?
I should have elaborated, but basically what MD87 replied. During the development of .NET it was decided that every exception caused by programs should inherit from ApplicationException, and all system errors should inherit from SystemException. Unfortunately .NET devs didn’t follow this and now everything should just inherit Exception since it’s easier to check. Interestingly, both SystemException and ApplicationException seem functionally identical to Exception.
Which actually makes sense. Java logic with exceptions that you cannot catch is a practice no other language has.
Apparently. (Source: https://stackoverflow.com/questions/5685923/what-is-applicationexception-for-in-net)