Build dlls with binary compatibility

[Benjamin Lukner]

Hi!

With .Net the programmer should deploy every program and all dlls in
separate folders.
Of course I want it to be different ;-)
I have several exe files using all the same dll in one directory. I
update the dll and deploy one exe with the new dll into that directory.
Now only that single exe will work. All other exe files can't use it any
more. With VB6 ("all things were better in the glory days" *g*) it was
possible to create the dll once and use it with binary compatibility to
create new versions of it without the need of rebuilding all exe files.

Is something like that still possible or am I doing something wrong?

(I can't put every exe and dll in a separate folder because the flash
memory is limited...)

Kind regards,

Benjamin Lukner

 

[Peter Foot [MVP]]

This is because you are changing the version of the dll hence it's unique
signature. Your options are:-

Place the different apps in separate folders each with their own versions of
the dlls.

Update all the exes compiled against the new dlls each time

Hard code the major minor and build version and only increment the revision
number in the dll - however this is only practical for bug fixes if you
change the exposed functionality you should change the version number too.

Peter