Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
User on the client side decides what assemblies are going to be needed for the .net user code on the driver.
Even if there are multiple versions of the same dll referenced by the various components in the project, only one physical dll and version will make it to the driver.
On the driver side, we should map different version load requests to this single dll version.
Attachments
Issue Links
- is related to
-
REEF-642 Remove custom assembly loading logic
- Resolved