namespace confilct....

[Jéjé]

Hi,

I'm using the ADOMD.Net 9 in my web site + a third party web control which
used the ADOMD.Net 8.0.

Everytime I compile my web site in VS 2005, a referecne to the 8.0 library
is added this cause a namespace conflict.
So I must remove the 8.0 reference in the web.config and the site works fine
Only the compilation doesn't works, so its long to debug.

how can avoid this behavior?
can I bypass or explicitly reference a particular version of the assembly
in my code like:
Imports MyNameSpace=<version 9>.Microsoft.AnalysisServices

or can I do something in my web.config to insure that the third party
control will not add the assembly entry?

thanks.

Jerome.

[Kevin Spencer]

Let's say you have 2 namespaces, in 2 different assemblies: name1 and name2.
Each namespace has a class called foo. You are using both namespaces in a
Page. You are also using an instance of the name1.foo class in your Page. At
the top of the page, you have:

using name1;
using name2;

Now, later on down in the page, you declare a field that is of type
name1.foo:

private foo bar;

The compiler cannot tell from this whether you are referring to name1.foo or
name2.foo. To remedy this, change the code to read:

private name1.foo bar;

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Jéjé" <willgart_A_@hotmail_A_.com> wrote in message
news:eV**************@TK2MSFTNGP02.phx.gbl...

Hi,

I'm using the ADOMD.Net 9 in my web site + a third party web control which
used the ADOMD.Net 8.0.

Everytime I compile my web site in VS 2005, a referecne to the 8.0 library
is added this cause a namespace conflict.
So I must remove the 8.0 reference in the web.config and the site works
fine
Only the compilation doesn't works, so its long to debug.

how can avoid this behavior?
can I bypass or explicitly reference a particular version of the assembly
in my code like:
Imports MyNameSpace=<version 9>.Microsoft.AnalysisServices

or can I do something in my web.config to insure that the third party
control will not add the assembly entry?

thanks.

Jerome.

[Jéjé]

no,

2 namespaces, 1 assembly but 2 different version of this assembly (version
8.0 and 9.0)!

there is no imports section in my code for the moment.

these 2 versions of the assembly contains the SAME namespace
But the version 9.0 provides more classes under the namespace.

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:ex**************@TK2MSFTNGP04.phx.gbl...

Let's say you have 2 namespaces, in 2 different assemblies: name1 and
name2. Each namespace has a class called foo. You are using both
namespaces in a Page. You are also using an instance of the name1.foo
class in your Page. At the top of the page, you have:

using name1;
using name2;

Now, later on down in the page, you declare a field that is of type
name1.foo:

private foo bar;

The compiler cannot tell from this whether you are referring to name1.foo
or name2.foo. To remedy this, change the code to read:

private name1.foo bar;

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Jéjé" <willgart_A_@hotmail_A_.com> wrote in message
news:eV**************@TK2MSFTNGP02.phx.gbl...

Hi,

I'm using the ADOMD.Net 9 in my web site + a third party web control
which used the ADOMD.Net 8.0.

Everytime I compile my web site in VS 2005, a referecne to the 8.0
library is added this cause a namespace conflict.
So I must remove the 8.0 reference in the web.config and the site works
fine
Only the compilation doesn't works, so its long to debug.

how can avoid this behavior?
can I bypass or explicitly reference a particular version of the
assembly in my code like:
Imports MyNameSpace=<version 9>.Microsoft.AnalysisServices

or can I do something in my web.config to insure that the third party
control will not add the assembly entry?

thanks.

Jerome.