Hi folks,
i've posted this with no response on a few other lists this week, and
would be extra grateful of any help..

I know .NET is supposed to solve dll hell, but I'm having trouble
getting my
assemblies to work the way I want them to.

I have 5 dlls in my winforms app, all strong named, and with versions
specified to 1.0.* in
assemblyInfo.cs for each project.

What I want to do periodically is replace any one of the dlls with a
new
build. However, when I do this, I get a FileLoadException with
additional
information:
"The located assembly's manifest definition with name 'MyDLL' does not
match
the assembly reference."

I'm guessing this is behaviour by design, and the assembly that
references
the updated one won't accept a new version. I can solve the problem by
recompiling all the assemblies in VS so that they pick up any updated
references,
but that is a pain, and just replacing one dll on the server is way
simpler,
if its possible.

How do I make the assemblies not be fussy about what version of
referenced
assemblies is loaded? i will obviously be sure that there is no change
in method signatures, and if there is a change, then replace all the
dlls that need to be updated at the same time.

Thanks
Tim