Microsoft Technology Licensing, LLC

David Ellis Pugh

Mark Alistair Wilson-Thomas

Monty Hammontree

Steven Clarke

Brandon C Adams

Zachary S Zaiss

Murali Krishna Hosabettu Kamalesha

Daniel R Dole

Vu Minh Le

Gustavo Araujo Soares

Arjun Radhakrishna

John Sells Tilford

German David Obando Chacon

Oleg Tkachenko

Piyush Arora

Sumit Gulwani

Anson Michael Horton

Ashish Tiwari

Peter Groenewegen

Ivan Radicek

Titus Barik

Wode Ni

Ameya Sanjay Ketkar

Alexey Svyatkovskiy

Shengyu Fu

Andrew R Sterland

Shao Kun Deng

Kesavan Shanmugam

Gregory Bernard Miskelly

Srivatsn Narayanan

John Eugene Ball

Erich Gamma

Vivian Julia Lim

Alexandru Ioan Dima

Hemchander Venkateshwara Sannidhanam

Jonathan Keith Simmons

Anqi Li

Jason Ronald William Ramsay

Guillaume Jenkins

Jui Hanamshet

Christian David Gunderman

Shwetha Srinath

Jin Woo Jang

Aaron Chak Hei Yim

Jack Tilford

Paul Van Brenk

Daniel Lebu

During software development, embodiments find various kinds of weak spots in source code and automatically suggest fixes to strengthen the code, without requiring developers to expressly select weakness finder mechanisms or fixer mechanisms by navigating a development tool's menu system. Weakness finders may analyze code using items such as hole detection, diagnostic errors, test results, changed code matches, prospective code discrepancies, generated code confidence scores, generated suggestion competition, and artificial intelligence. Weak spots and their context are submitted to weak spot fixers, which may generate fix suggestions using functionalities such as code synthesis, refactoring, autocompletion, retesting, and artificial intelligence. Fix candidate sets may be evaluated for consistency, diagnostic errors, and discrepancies. Snippets may be dynamically filled for presentation to a user.

Syntax subtree code strengthening

Edit automation functionality generalizes edits performed by a user in a document, locates similar text, and recommends or applies transforms while staying within a current workflow. Source code edits such as refactoring are automated. The functionality uses or provides anchor target lists, temporal edit patterns, edit graphs, automatable edit sequence libraries, and other data structures and computational techniques for identifying locations appropriate for particular edits, for getting transforms, for selecting optimal transforms, for leveraging transforms in an editing session or later, and for displaying transform recommendations and results. The edit automation functionality enhances automation subtool generation, discoverability, and flexibility, for refactoring, snippet insertion, quick actions in an integrated development environment, and other automatable edit sequences.

Edit automation using an anchor target list

Edit automation using a temporal edit pattern

Distinguishing pattern differences from non-pattern differences. A set of differences is identified. The set comprises a plurality of differences between first and second versions of a document. A pattern is identified. The pattern explains a transformation from a first string in the first version of the document to a second string in the second version of the document. A subset of differences are identified. The subset comprises a plurality of differences, from among the set, which match the pattern. While presenting a user interface that visually highlights differences between the first and second versions of the document, a first visual treatment is applied to a first difference, based on the first difference being included in the subset. A second visual treatment is also applied to a second difference, based on the second difference being excluded from the subset. The second visual treatment is different than the first visual treatment.

Distinguishing pattern differences from non-pattern differences

Edit automation enhancements may be implemented in source code editors and other text editors. Provisional selections that indicate user intentions are submitted to a suggestion generator with other edit context information, to improve the quality of generated text suggestions and reduce the cognitive load on users. A provisional selection may include a highlighted completion list entry, or document text targeted by a hovering cursor, or metainformation text targeted by the hovering cursor, for example. An inline grey text suggestion driven by provisional selection may be displayed simultaneously with completion list suggestions that were created without regard to provisional selection. Suggestions driven by provisional selection may be interleaved with existing document text. Suggestions may be accepted fully in one gesture, or in parts. Suggestions may be edited by a user before being accepted, driving further suggestion refinement. Multiple suggestions may be displayed simultaneously, reducing pressure on the suggestion generator.

Provisional selection drives edit suggestion generation

Embodiments automate surfacing of underutilized development tool features, thereby enhancing the discoverability of subtools, commands, shortcuts, settings, visualizers, and other tool features. After spotting an inefficiency in the user's interaction with one or more tools, the feature surfacing functionality offers the user an interaction optimization suggestion. A mapping structure correlates detected interaction patterns with objectively better interaction optimizations. Several examples of mappings are discussed. The user can accept a suggestion, have the suggested optimization applied by an enhanced tool, and thereby reduce the number of user gestures utilized to accomplish a desired result, reduce the number of tools utilized, increase security, reduce risk of error, or get to the desired result faster, for example. Interaction optimizations also help the user stay focused, by reducing or avoiding departures from the user's current primary workflow. Other aspects of tool feature surfacing functionality are also described herein.

Surfacing underutilized tool features

Embodiments relate to incorporating supplemental information into a code editor's editing view that may make the code more understandable to those not familiar or comfortable with the code. The editor receives adornments that may be translations or semantic equivalents of constructs already in the code. The editor adds the adornments to an editing view for editing the source code. The adornments are inserted into lines of the source code displayed in the editing view and have some of the appearance of the source code in the editing view. The adornments are passive with respect to the source code; they are not necessarily compiled or saved. The adornments may be tokens provided by a compiler and/or an integrated development environment. The editor may apply heuristics or rules to determine which adornments are to be used and where they will be inserted.

In-line code adornments

Tracking edits executed against a file to ensure that the edits are monitored consistently so that language service requests are properly handled. Initially, a collaboration session is established. This collaboration session includes an owner and a participant computer system. Then, the owner computing system receives messages that are directed toward a file stored by the owner computer system. These messages include edits that are to be performed against the file and language service request(s). A file version is then assigned to a subset of these edits. As the subset of edits are executed against the file, the file's state changes. The file versions are published to both the participant computer system and to a language service running on the owner computer system. The language service uses the published file versions to track the edits that are being executed against the file and to respond to the language service request(s).

Responding to requests by tracking file edits

Facilitating navigating presentations of data structures in a computing environment. A method includes detecting user input for navigating to a location in a presentation of a data structure stored at a computing system. The method further includes as a result of detecting user input for navigating to a location in the presentation of a data structure, outputting from an accessibility compliant interface at the computing system, at least a portion of a notification identifying the location in the presentation of a data structure. The method further includes, as a result of detecting user input for navigating to a location in the presentation of a data structure, outputting from the accessibility compliant interface at the computing system, at least a portion of an enumeration of tokens for predetermined items of import relevant to the location.

Accessible metadata in data structures

Disclosed herein is a system and method for optimizing a developer's ability to find and navigate relevant documents, relationships, and other information related to an identifier in the code they are developing. An inline viewport is presented to the user in response to the user selecting an identifier in the code whereby the user is able to see relevant information related to the identifier in a spatially consistent location with the code they are investigating. Further, the developer has the ability to make changes to the code in the viewport without leaving the current editor.

Inline display and preview of related information for elements in a document

Disclosed herein is a system and method for optimizing a developer's ability to find and navigate relevant documents, relationships, and other information related to an identifier in the code they are developing. An inline viewport is presented to the user in response to the user selecting an identifier in the code whereby the user is able to see relevant information related to the identifier in a spatially consistent location with the code they are investigating. The developer further has the ability to cascade the viewports such that multiple levels of depth of relationships can be viewed in the viewport.

Cascading inline display and preview of related information for elements in a document

A 'safe zone' can be created within which the effect of the actual cursor position is overridden when selecting content. The start position and the end position of the selection can be compared. If the selection is a forward selection but the cursor position has moved upwards, the vertical component of the cursor position is overridden by the vertical position of the cursor at the start of the selection. If the selection is a reverse selection but the cursor position has moved downwards, the vertical component of the cursor position is overridden by the vertical position of the cursor at the start of the selection. The safe zone can have any kind of shape.

Directional selection

Growing community of inventors

Bellevue, WA, United States of America

David Ellis Pugh