Can References to "Oracle.DataAccess" AND "System.Data.OracleClient" co-exist in one application ?

[Peter Kanurer]

Assume I add in VisualCSharp 2005 References to

Oracle.DataAccess

AND

System.Data.OracleClient

to an application. Does this cause problems or can they co-exist in one application ?

Peter

[Mr. Arnold]

"Peter Kanurer" <pe*******@yahoo.co.ukwrote in message
news:46***********************@newsspool3.arcor-online.net...

Assume I add in VisualCSharp 2005 References to

Oracle.DataAccess

AND

System.Data.OracleClient

to an application. Does this cause problems or can they co-exist in one
application ?

One is in the System namespace and one in in the Oracle namespace or two
different dll(s). So, you can use them both with in one application. You can
use them both in the same class if it came down to that it, but I don't know
why anyone would do it. It's either one or the other. I think you would need
the Oracle DataAccess if you needed to work with CLOB or BLOB data, as I
don't think the one in System can do that.

[BLUE]

I think you can, but you have to use Namespace.X when X is defined in both
namespaces (however the compiler will tell you there is an ambiguous
reference).
HTH,
Luigi.

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Peter Kanurer wrote:

Assume I add in VisualCSharp 2005 References to

Oracle.DataAccess

AND

System.Data.OracleClient

to an application. Does this cause problems or can they co-exist in one application ?

They can.

But I think you are asking for problems. Use one or another.

Arne

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Arne Vajhøj wrote:

Peter Kanurer wrote:

>Assume I add in VisualCSharp 2005 References to

Oracle.DataAccess

AND

System.Data.OracleClient

to an application. Does this cause problems or can they co-exist in
one application ?

They can.

But I think you are asking for problems. Use one or another.

And I am not talking about namespace & compile problems but
about the problem of accessing the same data through two
providers.

Arne