Application dependencies

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is it possible to only replace the EXE of an application without replacing
its dependency DLL's (or replace one of the DLL's without replacing anything
else)? When I've tried this before, the application blew chunks until I also
replaced its denpendency DLL's.
 
Todd said:
Is it possible to only replace the EXE of an application without
replacing its dependency DLL's (or replace one of the DLL's without
replacing anything else)? When I've tried this before, the
application blew chunks until I also replaced its denpendency DLL's.

In the context of .NET? Yes.

If the library assemblies do not change then the new process assembly
will be compiled against the old library assemblies. This means that the
manifest of the process will have the name of the old libraries and so
you only need to deploy the process. When the process is run .NET will
locate and load the old libraries.

Actually it is worse than that. If a library does not have a strong name
then versioning will be turned off and Fusion will merely look for a
library with the short name in the current folder (or in the folder with
the short name, or a subfolder mentioned in the config file). In this
case *any* DLL with the appropriate name will be loaded.

Richard
 
Back
Top