Hi,
I have struggled for several hours with this issue until I've
understood and solved my problem. However, my solution isn't
necessarily an optimal one, and worse - I think that my understanding
lacks something.
The situation which I have is the following (I will try to 'simplify'
the problem):
I have a utilities assembly which is strongly signed. The assembly is
registered both on my machine and a target server. An older
application of mine works just fine.
However, both the utilities dll and a newer application are using a
COM component (CDO, but this doesn't really matter). The newer
application is also using the utilities dll.
I have had the "The located assembly's manifest..." error, and I
puzzled by it. To make a story short, I was forced to use the same key
file I used for the utilities assembly, in order to create the same
COM interop CDO (i.e. generated with an indentical public key).
This solved the problem, but do I have to use the same key file in an
assembly which uses another assembly, and *both* of them use the same
interop ?
If so (and I'm sure there's a way out of this), what happens if you
have another "utilities" assembly, which uses a different key file,
and both your assembly and the new utilities assembly use the same
interop ? I reckon you can't use two key files.
Thanks,
Elad
