By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,338 Members | 1,350 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,338 IT Pros & Developers. It's quick & easy.

Inheritance design question

P: n/a
I'm not an OOP guru, but I would say ". . .not necessarily"

What if the base class and derived classes are internal?
Then the base class has to be within the same assembly to
be inherited from. You may want to create several classes
that are used throughout the assembly, but are not
accessible outside the assembly. . .

If your base class will be inherited across multiple
assemblies and future applications, then I would then
consider throwing it (the base class) into it's own
assembly (class library).

In terms of inheritance guidelines just always keep in
mind," IS A [object type] (inheritance candidate), or HAS
A [object type](composition candidate)".
-----Original Message-----
Hello oop gurus,

I'm using VB.NET and trying to define a best practice design approach whileimplementing inheritance into our application design.. I think I know theanswer to this, just want some clarification from the pros.. If I have abase class in the same assembly as the derived class is this considered poordesign..? I would think yes, it would seem you would want clear seperationbetween your base class and derived class.. I'm relatively new toinheritance, but understand the basics. I want to prepare myself to beginmaking design related decisions regarding the use and implementation ofinheritance in our apps, if anyone knows where I can find some designguidelines relating to inheritance I would very much appreciate it..


Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.