Abstract: A server exposes debugger services to a plurality of debugger clients. One or more debugger clients can select a debug operation and establish a debug session in a thread of a server process for debugging user code. A two-way debug communication pipeline can be established between a debugger client and the server using standard encoding protocols and standard network transport protocols. A two-way debug communication pipeline can be established using HTTP where the server can initiate a communication with the debugger client using a long polling technique. When one of the threads of the server process is suspended, the other threads in the server process continue to execute.

Abstract: A server exposes debugger services to a plurality of debugger clients. One or more debugger clients can select a debug operation and establish a debug session in a thread of a server process for debugging user code. A two-way debug communication pipeline can be established between a debugger client and the server using standard encoding protocols and standard network transport protocols. A two-way debug communication pipeline can be established using HTTP where the server can initiate a communication with the debugger client using a long polling technique. When one of the threads of the server process is suspended, the other threads in the server process continue to execute.

Abstract: Communicating between managed add-ins and COM hosts. A computing environment includes host objects which may be one of a COM object or a managed code object. The computing environment further includes add-in objects implemented in managed code. Add-in object can provide additional functionality to the host objects. A method includes acts for communicating between add-in objects and host objects. The method includes determining that a first host object to be communicated with is a COM object of a COM host. As a result of determining that a host object to be communicated with is a COM object, incoming and outgoing communications from a managed code add-in are routed through an interop proxy. The interop proxy is implemented in managed code with a managed code add-in. The interop proxy is configured to translate managed code invocations to COM code invocation, and to translate COM code invocations to managed code invocations.

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: Architecture that integrates an unmanaged application as a hosted application into a design environment in a coherent yet usable manner such that the developer can use the hosted application's native functionality yet leverage rich productivity features provided by the IDE. The IDE includes a hosting component that comprises an application adaptor for providing an interface from the unmanaged application to the IDE. The IDE further includes a designer framework that provides user access to designer capabilities of the IDE. The host adaptor interfaces to the designer framework either directly and/or through an integration interface. Thus, the developer/user can then access the native functionality of the unmanaged application as well as the IDE functionality. This provides rich integration between the development environment and the hosted application, the end result of which is the designer interacting with the IDE.

Abstract: Communicating between managed add-ins and COM hosts. A computing environment includes host objects which may be one of a COM object or a managed code object. The computing environment further includes add-in objects implemented in managed code. Add-in object can provide additional functionality to the host objects. A method includes acts for communicating between add-in objects and host objects. The method includes determining that a first host object to be communicated with is a COM object of a COM host. As a result of determining that a host object to be communicated with is a COM object, incoming and outgoing communications from a managed code add-in are routed through an interop proxy. The interop proxy is implemented in managed code with a managed code add-in. The interop proxy is configured to translate managed code invocations to COM code invocation, and to translate COM code invocations to managed code invocations.

Abstract: A managed automation programming model is provided for versioning computing components independently, isolating such components, and dynamically binding them. For example, components such as an application and an and-in are able to version independently of one another, so that disparate versions of these components are still able to communicate—or in the nominal case, the same versions are able to communicate. Moreover, such components are isolated by the managed automation programming model so that they can be disintegrated and bound with other components in a seamless manner. Lastly, the independent versioning and component isolation advantageously allows for dynamic binding of the components at runtime.

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: A system that facilitates menu management in an OLE document environment. The system includes a menu component that receives a server menu of a server application with a container menu of a container application. The menu component detects a menu conflict between the menus. The system further includes a conflict component that resolves the conflict between a server menu item of the server menu and a container menu item of the container menu, wherein at least one of the server menu item and the container menu item is modified to be unique from the other. The conflict component then outputs the integrated final menu.