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

[colin]

Hi,
I started to get this warning, I have two executables wich share the same
file,
so I have included one .exe as a reference to the other.

but I dont know how I have two versions of the same thing,
or even what things exactly they are refering to.

it gives me an option of adding a 'fix' but I dont like this unless I know
whats going on
or I might end up with changes not being aplied to bith.

any ideas what this is exactly or how to find more about it?
ie wich module etc.

I have tried removing the reference and re adding it but with no success.

thanks
Colin =^.^=

[colin]

"colin" <co*********@ntworld.NOSPAM.comwrote in message
news:aX***************@newsfe7-win.ntli.net...

Hi,
I started to get this warning, I have two executables wich share the same
file,
so I have included one .exe as a reference to the other.

but I dont know how I have two versions of the same thing,
or even what things exactly they are refering to.

it gives me an option of adding a 'fix' but I dont like this unless I know
whats going on
or I might end up with changes not being aplied to bith.

any ideas what this is exactly or how to find more about it?
ie wich module etc.

I have tried removing the reference and re adding it but with no success.

ah, a bit of gueswork I found the zedgraph module I had used in both
applications was not the same,
I had referenced the same dll in both, so I dont know why they were
differemt,
maybe it makes local copies, I gues it is included in the referenced .exe
file
but if i remove zedgraph from the reference it wont build.
so I just re referenced zedgraph.

is there a tidier way to use the same file in two .exe so any changes are
always guaranteed to be included in both .exe?
and preferably to be able to modify it from either project.

it seems hell bent on stopping me doing this by making local copies etc.

Colin =^.^=