.net - Base business class: is it bad? -
I want to create my base business class, such as some entrybase, to perform some normal behavior, such as to track Applying the interface changes in the object (Isu, iSdist) and the Innopefproiti Change Interface
But many people say that it is a bad idea to keep a base business class and get it from all your business objects. Generally, they say it is bad to present the presentation code in the institution class. But I think that this is just a theory. What is bad in practice? They say: Try it yourself, there is usually no other debate.
So what do you guys think? Is it good or bad? If bad, why? Please, try to be a practical person, not a theoretical person.
Many people's thoughts, which say that there should be only one area of responsibility in a classroom. By state tracking, rendering and further building in a common base class, you will definitely violate SRP. If you class handle many tasks, then there will be several reasons for this to change.
Comments
Post a Comment