Since you (seem) to want to use multiple inheritance to solve code reuse
issues, not the substitution principle, why not favor "composition over
inheritance"? Build up a single common code class (using generics if
necessary), and expose it as a property off your inherited controls. If
you want to b
What if you use composition? Create a new class to contain all your
shared functionality, then in each control class create an instance
variable of that type. That way you don't have to implement the code in
multiple places. Like:
public class MyCommonFunctionality
public sub Method1
end sub
.
On 16/2/07, Jonathan Heizer <[EMAIL PROTECTED]> wrote:
Hey all,
I am trying to reuse a bunch of Class members, properties, and functions
that are shared across multiple classes. Each of these classes already
inherit form a web control so I can not create a base class supporting the
function sin
