I don't think interfaces are suitable in this situation because I am providing common functionality in the base classes and the using the template method design pattern to allow developers to plug-in the pieces of functionality that vary.
Unfortunately, the developers also have to create empty...
I'm happy with the base classes and subclasses. But I'm also trying to encapsulate the relationships between the classes in the base classes, i.e. BasePage calls BaseBll which calls BaseDAL.
When a developer implements a specific instance of this framework they will have to subclass all the...
I'm trying to write a set of abstract classes which call each other encapsulating the common functionality of a particular task. Each of the classes will alo contain some abstract methods where non-generic code can be plugged in, e.g.
BasePage -> BaseBLL -> BaseDAL
The way I have come up with...
When writing OO code I quite often use the constructor to pass sub class instances which means my sub classes always have a constructor like the C# example below. Is this ok or is their a better way?
class baseClassA
{
protected baseClassB m_ClassB;
public baseClassA(baseClassB classB)
{...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.