You must log in or register to comment.
https://stackoverflow.com/a/5685943
Here is the answer, M$ changed their mind at some point and your university has a stale information but it seems it was true in the past.
This is a reucurring theme at this specific subject unfortunately. He doesn’t seem to put much effort into it, as most slides are just plain text and nothing else. I stopped attending after the second class.
That truly sucks. Yeah, some professors can be like that. I had a math professor offer bonus points to the first 3 students completed the assignment, only for the majority to cheat and just look up the answer and turn that in. It became a contest of who could copy the fastest and one student even admitted to doing it, but she just didn’t care and gave points to the cheaters anyway.
I swear all lecturer slides are outdated for programming.
Thanks for looking that up, because the application exception is the way I originally learned this myself. And I’ve been doing .net for 20 years.
Do you guys still use it in practice though? I have never seen or heard about this until now.
I don’t create many exceptions in c#. The way I handle errors doesn’t require it for (damn near) everything. Java makes throwing named errors more important, and consequently I wrote more for Java.
M$ Docu sounds like that doesn’t make sense, do you have some more context?
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.
Apparently. (Source: https://stackoverflow.com/questions/5685923/what-is-applicationexception-for-in-net)
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.
I have never extended from or caught an application extension in my entire career. Agree with Microsoft, if it’s an application exception it’s coming from the framework. All of mine derive from exception.
