Abstract: Shared libraries and references within the shared libraries can be retargeted in accordance with optional transformation rules. The optional transformation rules can be applied differently for different binding contexts. For user-code scenarios, optional retargeting binding rules can be applied automatically by default without requiring any human intervention. Optional targeting that triggers automatic binding behaviors can be disabled based on heuristics. Alternatively, the user can specify in the code or in a configuration file if the source or target is to be loaded. Transformation rules can be disabled based on heuristics. A manual option permits a user to choose at runtime whether the transformation is to be applied, or not applied, in a late-bound fashion.

Abstract: Shared libraries and references within the shared libraries can be retargeted in accordance with optional transformation rules. The optional transformation rules can be applied differently for different binding contexts. For user-code scenarios, optional retargeting binding rules can be applied automatically by default without requiring any human intervention. Optional targeting that triggers automatic binding behaviors can be disabled based on heuristics. Alternatively, the user can specify in the code or in a configuration file if the source or target is to be loaded. Transformation rules can be disabled based on heuristics. A manual option permits a user to choose at runtime whether the transformation is to be applied, or not applied, in a late-bound fashion.

Abstract: Different views on an object that has metadata. For instance, one code segment might have one view of the object and be able to view some of the metadata of that object, while another code segment might have a different view of the object and have a view on a different set of the metadata of that object. This may be done even though the code segments reside in the same application. Thus, each code segment may have a view of the metadata on the object that is most useful for that code segment to use the object without getting confused by metadata that is less or not relevant to the manner in which the code segment is to use the object.

Abstract: Different views on an object that has metadata. For instance, one code segment might have one view of the object and be able to view some of the metadata of that object, while another code segment might have a different view of the object and have a view on a different set of the metadata of that object. This may be done even though the code segments reside in the same application. Thus, each code segment may have a view of the metadata on the object that is most useful for that code segment to use the object without getting confused by metadata that is less or not relevant to the manner in which the code segment is to use the object.