question about inheritance and Imports statement

  • Thread starter Thread starter BillE
  • Start date Start date
B

BillE

Does a subclass have to import namespaces which were already imported by the
superclass?

I have a base class which imports the System.Data.SQLClient namespace to use
the dataset member.

When I inherit this base class, the subclass must also import the
System.Data.SQLClient namespace to use its members.

I thought that a subclass would not have to re-import namespaces which were
already imported by the superclass.

Do I understand correctly, or am I doing something wrong?

Thanks
Bill
 
If you go to your project properties -> References, you can import the
reference for the entire project, rather than doing it on a file by file
basis.
 
Robinson said:
If you go to your project properties -> References, you can import the
reference for the entire project, rather than doing it on a file by file
basis.
Click to expand...


You cannot use the Imports statement without first adding a reference
to the corresponding assembly. In other words you cannot add a
reference on a file by file basis. References are *always* added a
project level.

That said, the Imports statement has nothing to do with inheritance.
It is simply a means of easing the amount of typing a developer has to
do. Internally, the compiler works with the fully qualified type name.
 
You cannot use the Imports statement without first adding a reference
to the corresponding assembly. In other words you cannot add a
reference on a file by file basis. References are *always* added a
project level.

That said, the Imports statement has nothing to do with inheritance.
It is simply a means of easing the amount of typing a developer has to
do. Internally, the compiler works with the fully qualified type name.
Click to expand...

Yes, but you can add a reference to the assembly AND import the namespace in
project settings.
 
Robinson said:
Yes, but you can add a reference to the assembly AND import the namespace in
project settings.
Click to expand...

Ah yes! Your first post said "References" so I was thinking about
adding a reference to another assembly, when you were actually
referring to the References section in the properties page and the
Imported Namespaces section on that.

I primarily use C# which does not have this feature, hence my
puzzlement.
 
Back
Top