RE: Circular conflict using ADOMD in Visual Studio
From: Andrew Wiles (AndrewWiles_at_discussions.microsoft.com)
Date: 01/28/05
- Next message: johnny: "calling ADSI objects from Web Application"
- Previous message: Patrick Philippot: "Re: Any reason NOT to strong-name an assembly?"
- In reply to: Andrew Wiles: "Circular conflict using ADOMD in Visual Studio"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 Jan 2005 00:21:03 -0800
Hmmmmm
I have found a partial explanation for my problem. I also include a
reference to DSO version 5.1. It appears that it is the introduction of the
DSO reference that is causing the dependency to ADODB 2.7.0.0. Is it possible
that referencing DSO and ADOMD is not allowed?
"Andrew Wiles" wrote:
> Hi
>
> I have a project which uses ADOMD (Version 2.8.0.0) as a reference. This
> automatically includes the ADODB interop assemly as well as ADOMD.
>
> When I build this project I am getting a warning message....
>
> "Warning: The dependency 'Interop.ADODB, Version 2.7.0.0, Culture=neutral in
> Project 'ITWOlapControls' cannot be copied to the run directory because it
> would overwrite the reference 'Interop.ADODB, Version 2.8.0.0,
> Culture=neutral'
>
> Note: The reference to ADOMD 2.8 is the only reference associated with this
> project.
>
> The project will build in spite of the warning, however if the assembly
> created is included as a reference in another project I get the conflicting
> errors...
>
> "Error: The dependency 'Interop.ADODB, Version 2.7.0.0, Culture=neutral in
> Project 'ITWOlapControls' cannot be copied to the run directory because it
> would overwrite the reference 'Interop.ADODB, Version 2.8.0.0,
> Culture=neutral'
>
> and
>
> "Error: The dependency 'Interop.ADODB, Version 2.8.0.0, Culture=neutral in
> Project 'ITWOlapControls' cannot be copied to the run directory because it
> would overwrite the reference 'Interop.ADODB, Version 2.7.0.0,
> Culture=neutral'
>
> and the second project will not build.
>
> Note: If I add the original reference as a 2.7 reference I get exactly the
> same behaviour.
>
> This is on a new PC that has been configured with windows XP + SP2, Visual
> Studio .Net 2003 Enterprise, SQL Server + SP3a
- Next message: johnny: "calling ADSI objects from Web Application"
- Previous message: Patrick Philippot: "Re: Any reason NOT to strong-name an assembly?"
- In reply to: Andrew Wiles: "Circular conflict using ADOMD in Visual Studio"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|