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

question about inheritance and Imports statement

P: n/a
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
Nov 15 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
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.

"BillE" <be****@datamti.comwrote in message
news:eF**************@TK2MSFTNGP02.phx.gbl...
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


Nov 15 '06 #2

P: n/a
Robinson wrote:
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.

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.
>
"BillE" <be****@datamti.comwrote in message
news:eF**************@TK2MSFTNGP02.phx.gbl...
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
Nov 15 '06 #3

P: n/a
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.
Yes, but you can add a reference to the assembly AND import the namespace in
project settings.
Nov 15 '06 #4

P: n/a

Robinson wrote:
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.

Yes, but you can add a reference to the assembly AND import the namespace in
project settings.
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.

Nov 15 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.