Can .NET Fusion loader load assembly reference different than that in manifest? -
i thought knew how .net runtime loads assembly references @ runtime, situation has raised doubts myself.
i have assembly client.exe refers assembly thirdparty.dll (version 5.1.0.0).
client.exe refers assembly analytics.dll (2.1.0.0)
thirdparty.dll refers assembly analytics.dll (2.0.0.0) (note different version).
now when run client.exe, loads thirdparty.dll (5.1.0.0), analytics.dll (2.1.0.0) fine.
i wonder, why call thirdparty.dll not fail since manifest of thirdparty.dll has entry analytics.dll (2.0.0.0) , version not loaded in appdomain @ all. have analytics.dll (2.1.0.0). know there no breaking changes across 2.0.0.0 , 2.1.0.0, should case exception @ all?
Comments
Post a Comment