Warning 1 Found conflicts between different versions of the same dependent assembly.

Warning 1 Found conflicts between different versions of the same dependent assembly.

Postby dghundt » Tue 18 Sep 2007 20:01

I recently upgraded from mydirect.net version 3 to 4.
I did a fresh instal of visual studio and mydirect.net version 4.
The program appears to work fine with debug mode.
However, I still receive this warning in visual studio:

Warning 1 Found conflicts between different versions of the same dependent assembly. [program name here]

At first it was giving me a warning about the older version of mydirect , but that went away when I removed the old license and had version 4 put in a new one.
I still get this warning noted above.
Mydirect.net version 3 is definitely not installed on the computer.
Any way to remove this so it goes away?

Thanks!
dghundt
 
Posts: 38
Joined: Thu 24 Aug 2006 01:16

Postby Alexey » Wed 19 Sep 2007 08:12

Make sure that there are no old CoreLab.MySql.dll or CoreLab.Data.dll on your system.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby dghundt » Wed 19 Sep 2007 12:26

Thank you.
I have an older version of my end user application installed on my pc (which would have the older dll file in the same folder), but would that affect what visual studio sees during development and debugging?

In visual studio I open up my program, when I go to references, I see only one of each dll you mentioned.

I did a fresh install so version 3 was not installed previously.
The old version of my end user application was reloaded which may have had references to the older license (or other things).

When I go to references, add, I do see three corelab.data component names located in different paths. Here is what I see.

1. v. 4.20.14.0 program files/common files/corelab/dataproviders/4.20/net2/corelab.data.dll

2. v. 4.20.14.0 program files/corelab/mydirect.net2/corelab.data.dll

3. v. 4.0.8.0 programfiles/microsoft vs8/common 7/ide/public assemblies/corelab.dbtools.data.dll
dghundt
 
Posts: 38
Joined: Thu 24 Aug 2006 01:16

Postby Alexey » Thu 20 Sep 2007 08:34

Have you resolved the problem or not?
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby dghundt » Thu 20 Sep 2007 13:56

No, issue not resolved.
The information provided above was meant to help you see what may be causing this warning message. Sorry if I did not make this clear.
Thank you again.
dghundt
 
Posts: 38
Joined: Thu 24 Aug 2006 01:16

SAMPLE WEB PROJECT

Postby wdavet » Thu 20 Sep 2007 17:28

Alexey,

I e-mailed you a sample web project that produces this error on my system.

Thanks.

W. David Taylor
wdavet
 
Posts: 24
Joined: Mon 26 Feb 2007 16:57

Re: SAMPLE WEB PROJECT

Postby Alexey » Fri 21 Sep 2007 07:43

wdavet wrote:Alexey,

I e-mailed you a sample web project that produces this error on my system.

Thanks.

W. David Taylor

Which error?
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Alexey » Fri 21 Sep 2007 12:48

dghundt, are you sure that no old assembly is present on your system?
From your posts this is still unclear.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for MySQL