Although using Exceptions to control application flow is an anti-pattern but why some famous project do it?

mohammad ramezani 11

According to many references like here and here, using Exceptions to control application flow is an anti-pattern that is not recommended. (Because of performance issues, Less readable and etc).

But my question is why do many famous boilerplates or advanced tutorial projects have used Exceptions to control flows? Like here in Microsoft eShopOnContainers project which is used custom exception (OrderingDomainException) and also Here in sample-dotnet-core-cqrs-api which return an exception to handle business rules.

does anyone know about the reason behind this?

Jack J Jun 24,296 Reputation points Microsoft Vendor

2021-11-11T05:44:34.847+00:00

@mohammad ramezani , Since your problem is related to anti-pattern problem instead of c# problem. I recommend that you could ask the question in stackoverflow. By the way, you could see the following link, which may be helpful for your question.
Are exceptions as control flow considered a serious antipattern? If so, Why?
Why not use exceptions as regular flow of control?
mohammad ramezani 11 Reputation points

2021-11-11T08:10:12.203+00:00

@Jack J Jun Thanks for your response. The thing is at first I asked this in StackOverflow here but they labeled it by opinion-based :(
but I believe it's not opinion-based. Some people added some comments over there but it does not seem rational. So I kept going and put questions here.
The first links that you share are the link that I mentioned in my question in the stack. have a look, please. I believe there should be a nice answer for this question
I even asked here in the eShopOnContainer GitHub as a question issue but still, no one has answered.