Jwithout any further context, I'm gonna have to say "don't use exceptions for normal control flow"
Dwhat to use instead? result objects?
Ayou can catch them in a middleware
Dand do all checks about all type of exceptions?
Aprobably make them inherit from a of sorts, so you can generalize it somewhat
Abut yeah that's considered a bad pattern, because it becomes harder to track the logic flow
Dwhat about to make an exception filter for each controller action?
AI wish c# had some syntax for result types to make them less verbose
Dyes…
Ayeah, I think that's actually better
Abecause you can use the MVC action result system then
Dgood. probably I will use this approach
Jprobably a good bet
Jbut it all depends on context
Dfor what kind of context result objects will be better than exceptions?
Jmost stuff in web land, for example