The type or namespace name 'Net' could not be found

[Al Cadalzo]

I get the compile error:
"The type or namespace name 'Net' could not be found"
on this line of code:

Net.HttpWebResponse resp = null;

Here are my using directives:
using System;
using System.Data;
using System.Data.SqlClient;
using System.IO;

If I say 'System.Net.HttpWebResponse' then the error goes away.

I have a similar problem when I declare a SqlConnection

If I say SqlClient.SqlConnection I get the error, but If I say just
'SqlConnection' then it's OK.
It seems as though the 'using System' directive and the 'using System.Data'
directive are being ignored.

I assembly references to System, System.Data and System.XML.

I don't have any problem with the 'using System.IO;' directive.

Any ideas?

Thanks,
Al

[bB]

Add the following directive:

using System.Net;

Tim

"Al Cadalzo" <ca*****@hotmail.com> wrote in message
news:#o**************@TK2MSFTNGP10.phx.gbl...

I get the compile error:
"The type or namespace name 'Net' could not be found"
on this line of code:

Net.HttpWebResponse resp = null;

Here are my using directives:
using System;
using System.Data;
using System.Data.SqlClient;
using System.IO;

If I say 'System.Net.HttpWebResponse' then the error goes away.

I have a similar problem when I declare a SqlConnection

If I say SqlClient.SqlConnection I get the error, but If I say just
'SqlConnection' then it's OK.
It seems as though the 'using System' directive and the 'using System.Data' directive are being ignored.

I assembly references to System, System.Data and System.XML.

I don't have any problem with the 'using System.IO;' directive.

Any ideas?

Thanks,
Al

[Jon Skeet [C# MVP]]

Al Cadalzo <ca*****@hotmail.com> wrote:

I get the compile error:
"The type or namespace name 'Net' could not be found"
on this line of code:

Net.HttpWebResponse resp = null;

Yes. That's because the "using" statement doesn't mean you can use
partial *namespaces*, it just means you can use unqualified type names.

Just include:

using System.Net;

and then just use

HttpWebResponse resp = null;

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Al Cadalzo]

Thanks Tim.
I am used to the way you can use partial namespace in VB.NET.

Al

"bB" <ti*@aterminal.free-serve.co.uk.dontspamme> wrote in message
news:Oh**************@tk2msftngp13.phx.gbl...

Add the following directive:

using System.Net;

Tim

"Al Cadalzo" <ca*****@hotmail.com> wrote in message
news:#o**************@TK2MSFTNGP10.phx.gbl...

I get the compile error:
"The type or namespace name 'Net' could not be found"
on this line of code:

Net.HttpWebResponse resp = null;

Here are my using directives:
using System;
using System.Data;
using System.Data.SqlClient;
using System.IO;

If I say 'System.Net.HttpWebResponse' then the error goes away.

I have a similar problem when I declare a SqlConnection

If I say SqlClient.SqlConnection I get the error, but If I say just
'SqlConnection' then it's OK.
It seems as though the 'using System' directive and the 'using

System.Data'

directive are being ignored.

I assembly references to System, System.Data and System.XML.

I don't have any problem with the 'using System.IO;' directive.

Any ideas?

Thanks,
Al

[Al Cadalzo]

Jon,

Thanks alot. I guess it works a bit differently than the imports directive
I'm used to in VB.Net.

Al
"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Al Cadalzo <ca*****@hotmail.com> wrote:

I get the compile error:
"The type or namespace name 'Net' could not be found"
on this line of code:

Net.HttpWebResponse resp = null;

Yes. That's because the "using" statement doesn't mean you can use
partial *namespaces*, it just means you can use unqualified type names.

Just include:

using System.Net;

and then just use

HttpWebResponse resp = null;

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too