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

why "import namespace=" ..." if not necessary?

P: n/a
Hi,

1) In file test.aspx, i put:
<%@ Page Language="VB" AutoEventWireup="false" CodeFile="test.aspx.vb"
Inherits="test" %>
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>
....

In file test.aspx.vb, i put:
....
Dim oConnection As System.Data.OleDb.OleDbConnection
....
No problem.It works.
----------------------------
2) But if i put in test.aspx.vb:
....
Dim oConnection As OleDbConnection
....
I get the error: "type OleDbConnection is not defined"
---------------------------
3) if i remove the import lines in test.aspx: and put this in test.aspx.vb:
Dim oConnection As System.Data.OleDb.OleDbConnection
.....

it works too.

So my question: why putting the import namespaces in test.aspx, because in
any way, I have to use "Dim oConnection As
System.Data.OleDb.OleDbConnection" instead of "Dim oConnection As
OleDbConnection" ?

Thanks
Chris



Why then the import in test.aspx?


May 10 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi Chris,

If you want to write the script in the same aspx page then the Import
statement is required other wise it's not required.

Hope this is clear.

Balu

"Chris" wrote:
Hi,

1) In file test.aspx, i put:
<%@ Page Language="VB" AutoEventWireup="false" CodeFile="test.aspx.vb"
Inherits="test" %>
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>
....

In file test.aspx.vb, i put:
....
Dim oConnection As System.Data.OleDb.OleDbConnection
....
No problem.It works.
----------------------------
2) But if i put in test.aspx.vb:
....
Dim oConnection As OleDbConnection
....
I get the error: "type OleDbConnection is not defined"
---------------------------
3) if i remove the import lines in test.aspx: and put this in test.aspx.vb:
Dim oConnection As System.Data.OleDb.OleDbConnection
.....

it works too.

So my question: why putting the import namespaces in test.aspx, because in
any way, I have to use "Dim oConnection As
System.Data.OleDb.OleDbConnection" instead of "Dim oConnection As
OleDbConnection" ?

Thanks
Chris



Why then the import in test.aspx?


May 10 '06 #2

P: n/a
Hi Balu,

Thanks for replying, but i still don't understand.

In my first file (test.aspx)
----------------------------
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>

In my second file (test.aspx.vb)
--------------------------------
Dim oConnection As OleDbConnection
This doesn't work.

I have to put:
Dim oConnection As System.Data.OleDb.OleDbConnection
But then, if i remove the import lines from test.aspx, it still works.

So why putting those imports lines?

"balucris" <ba******@discussions.microsoft.com> wrote in message
news:04**********************************@microsof t.com...
Hi Chris,

If you want to write the script in the same aspx page then the Import
statement is required other wise it's not required.

Hope this is clear.

Balu

"Chris" wrote:
Hi,

1) In file test.aspx, i put:
<%@ Page Language="VB" AutoEventWireup="false" CodeFile="test.aspx.vb"
Inherits="test" %>
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>
....

In file test.aspx.vb, i put:
....
Dim oConnection As System.Data.OleDb.OleDbConnection
....
No problem.It works.
----------------------------
2) But if i put in test.aspx.vb:
....
Dim oConnection As OleDbConnection
....
I get the error: "type OleDbConnection is not defined"
---------------------------
3) if i remove the import lines in test.aspx: and put this in test.aspx.vb: Dim oConnection As System.Data.OleDb.OleDbConnection
.....

it works too.

So my question: why putting the import namespaces in test.aspx, because in any way, I have to use "Dim oConnection As
System.Data.OleDb.OleDbConnection" instead of "Dim oConnection As
OleDbConnection" ?

Thanks
Chris



Why then the import in test.aspx?


May 10 '06 #3

P: n/a
Import the namespaces in the file where you use them. If you want to use
the namespace in the vb file, import them there:

Imports System.Data
Imports System.Data.OleDb

Chris wrote:
Hi Balu,

Thanks for replying, but i still don't understand.

In my first file (test.aspx)
----------------------------
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>

In my second file (test.aspx.vb)
--------------------------------
Dim oConnection As OleDbConnection
This doesn't work.

I have to put:
Dim oConnection As System.Data.OleDb.OleDbConnection
But then, if i remove the import lines from test.aspx, it still works.

So why putting those imports lines?

"balucris" <ba******@discussions.microsoft.com> wrote in message
news:04**********************************@microsof t.com...
Hi Chris,

If you want to write the script in the same aspx page then the Import
statement is required other wise it's not required.

Hope this is clear.

Balu

"Chris" wrote:
Hi,

1) In file test.aspx, i put:
<%@ Page Language="VB" AutoEventWireup="false" CodeFile="test.aspx.vb"
Inherits="test" %>
<%@ import namespace="System.Data"%>
<%@ import namespace="System.Data.OleDb"%>
....

In file test.aspx.vb, i put:
....
Dim oConnection As System.Data.OleDb.OleDbConnection
....
No problem.It works.
----------------------------
2) But if i put in test.aspx.vb:
....
Dim oConnection As OleDbConnection
....
I get the error: "type OleDbConnection is not defined"
---------------------------
3) if i remove the import lines in test.aspx: and put this in test.aspx.vb: Dim oConnection As System.Data.OleDb.OleDbConnection
.....

it works too.

So my question: why putting the import namespaces in test.aspx, because in any way, I have to use "Dim oConnection As
System.Data.OleDb.OleDbConnection" instead of "Dim oConnection As
OleDbConnection" ?

Thanks
Chris



Why then the import in test.aspx?

May 10 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.