Abstract: Various technologies and techniques are disclosed for generating add-in bridges that allow hosts to be extended using a dynamic language. The system programmatically determines static requirements that an add-in is required to implement in order to integrate with a particular host. The system programmatically generates the add-in bridge to conform to the requirements of the particular host and to operate like a compiled add-in while actually calling dynamic language script files that are executed by a scripting engine. The add-in bridge is generated by generating a component for the add-in that contains at least one class to conform to the host requirements. A constructor is then generated for the class. For each method the add-in is required to implement, a respective method is generated in the class that provides a stub implementation but that calls dynamic-language script files to perform a desired functionality.

Abstract: Various technologies and techniques are disclosed for using annotations in contracts to generate views and adapters. A framework is provided that supports annotations that can be used in a contract to allow a user to express how one or more members of the contract should be represented in at least one view, and to express how to adapt the members in at least one adapter. Annotations can also be used to indicate which of the components should be programmatically generated. The contract is accessed and at least a portion of the at least one view and the at least one adapter are generated based on the annotations and other information contained in the contract. For example, source code can programmatically be generated for a host side view, an add-in side view, a host side adapter, and an add-in side adapter using the various contract details and the annotations.

Abstract: An embodiment not only instantiates a pipeline that allows communication between first and second executable nodes regardless of whether the nodes have compatible or incompatible interface views, but also structures the pipeline based on the relationship between the interface views so, for example, the pipeline does not consume unnecessary overhead or introduce unnecessary data-transfer delay. For example, an embodiment compares a first interface view of a first executable node to a second interface view of a second executable node. A first communication pipeline having a first structure is instantiated between the first and second nodes if the first view has a first pre-established relationship to the second view, and a second communication pipeline having a second structure is instantiated between the first and second nodes if the first view has a second pre-established relationship to the second view.

Abstract: An embodiment not only instantiates a pipeline that allows communication between first and second executable nodes regardless of whether the nodes have compatible or incompatible interface views, but also structures the pipeline based on the relationship between the interface views so, for example, the pipeline does not consume unnecessary overhead or introduce unnecessary data-transfer delay. For example, an embodiment compares a first interface view of a first executable node to a second interface view of a second executable node. A first communication pipeline having a first structure is instantiated between the first and second nodes if the first view has a first pre-established relationship to the second view, and a second communication pipeline having a second structure is instantiated between the first and second nodes if the first view has a second pre-established relationship to the second view.

Abstract: Various technologies and techniques are disclosed for generating add-in bridges that allow hosts to be extended using a dynamic language. The system programmatically determines static requirements that an add-in is required to implement in order to integrate with a particular host. The system programmatically generates the add-in bridge to conform to the requirements of the particular host and to operate like a compiled add-in while actually calling dynamic language script files that are executed by a scripting engine. The add-in bridge is generated by generating a component for the add-in that contains at least one class to conform to the host requirements. A constructor is then generated for the class. For each method the add-in is required to implement, a respective method is generated in the class that provides a stub implementation but that calls dynamic-language script files to perform a desired functionality.

Abstract: Various technologies and techniques are disclosed for using annotations in contracts to generate views and adapters. A framework is provided that supports annotations that can be used in a contract to allow a user to express how one or more members of the contract should be represented in at least one view, and to express how to adapt the members in at least one adapter. Annotations can also be used to indicate which of the components should be programmatically generated. The contract is accessed and at least a portion of the at least one view and the at least one adapter are generated based on the annotations and other information contained in the contract. For example, source code can programmatically be generated for a host side view, an add-in side view, a host side adapter, and an add-in side adapter using the various contract details and the annotations.