I joined a company and the project I'm working on have an event handler that extends the FirstChanceException functionality to log the exceptions. The logs are stored in a file and not registered to the console. All the controllers actions have try catch blocks and they ignore the exception in the catch (because it's being logged in the FirstChanceException event handler) and return a value so the user doesn't get any errors.
I have a strong feeling that this is an antipattern or a bad practice but I don't have any good arguments.
Do you find this a bad practice and why, what are the downsides of this approach?
To add a bit more context, I found annoying that they don't show logs in the console (I can't debug an app without logs on the console) so I configured it to show them in my dev environment. Latter on, I started to find random exceptions like sockets closing and ES operations failing. These exceptions don't show up if you remove the FirstChanceException event handler because they are being catch and handled by .Net code itself. So that's a downside but the don't even used logs in the console in the first place.