Abstract: Enhancements described support transparent remote execution of development tool extensions. Compute-intensive extensions may be executed on an extension machine external to a developer machine which runs a user interface renderer of the development tool. User interface extensions may run locally. Instead of sharing a filesystem, the renderer on the developer machine and an extension host and extension(s) on the extension machine may access distinct respective machine filesystems. Instead of spawning debug extension and other extension-support processes locally, the renderer may instruct the extension host or an extension host agent to spawn the processes remotely on the extension machine. Existing extensions and newly created extensions are binary-compatible with single-machine or multi-machine development tool deployments.

Abstract: A collaboration session is provided in which an owner computer system and a participant computer system are both members. Within this collaboration session, both the owner and the participant computer systems are provided access to a multi-file workspace's build instance. Here, the multi-file workspace and the build instance are both stored locally on the owner computer system. Further, this workspace includes multiple files of source code. As a result, the build instance is a build of that source code. Various debug commands that are directed to the build instance may be received. Some of these commands originate from the owner computer system while others originate from the participant computer system. These debug commands are then multiplexed, and the build instance is executed in accordance with the multiplexed debug commands. As a result of executing the build instance, debugging data is generated.

Abstract: Enhancements described support transparent remote execution of development tool extensions. Compute-intensive extensions may be executed on an extension machine external to a developer machine which runs a user interface renderer of the development tool. User interface extensions may run locally. Instead of sharing a filesystem, the renderer on the developer machine and an extension host and extension(s) on the extension machine may access distinct respective machine filesystems. Instead of spawning debug extension and other extension-support processes locally, the renderer may instruct the extension host or an extension host agent to spawn the processes remotely on the extension machine. No change is needed to extensions; existing extensions and newly created extensions are binary-compatible with single-machine or multi-machine development tool deployments.

Abstract: A collaboration session is provided in which an owner computer system and a participant computer system are both members. Within this collaboration session, both the owner and the participant computer systems are provided access to a multi-file workspace's build instance. Here, the multi-file workspace and the build instance are both stored locally on the owner computer system. Further, this workspace includes multiple files of source code. As a result, the build instance is a build of that source code. Various debug commands that are directed to the build instance may be received. Some of these commands originate from the owner computer system while others originate from the participant computer system. These debug commands are then multiplexed, and the build instance is executed in accordance with the multiplexed debug commands. As a result of executing the build instance, debugging data is generated.

Abstract: A method, computer program product, and system for defect form quality indication is described. A method may comprise providing, via one or more computing devices, an indication of a relative importance of a first data entry field included in a defect entry form. The method may further comprise determining, via the one or more computing devices, a first field quality level of user input corresponding to the first data entry field included in the defect entry form. The method may additionally comprise providing, via the one or more computing devices, an indication of the first field quality level of the user input corresponding to the first data entry field included in the defect entry form.