Microsoft Technology Licensing, LLC

Stephen Wharton Provine

John Joseph Rivard

Steven P Anonsen

Hartmut Maennel

Sam Spencer

Habib Heydarian

A user interface can be maintained in a responsive state on a user interface thread while synchronous application logic is running on a background thread. The application logic can access an object on the background thread, and the user interface can access the same object on the user interface thread. Additionally, a request for work to be done on an object can be received. If the request is to be dispatched to a background thread, then the work can be dispatched to the background thread without blocking the user interface thread. However, if the request is to be dispatched to the user interface thread, then the work can be dispatched to the user interface thread, and the background thread can be blocked.

Responsive user interface with background application logic for working on an object

Techniques for determining and tracking dependent properties for a calculated property are provided. A request for a value of a first property is received. The value for the first property is calculated, including accessing values for one or more properties used to calculate the value for the first property. The accessing of the values for the one or more properties may be detected, and the one or more properties may be tracked as dependent properties for the first property in a first set of dependent properties. A change in the value of a second property may subsequently be detected. If the second property is determined to be included in the first set of dependent properties, the value of the first property is invalidated.

Runtime dependency analysis for calculated properties

A system and method for providing DDEX (data designer extensibility) default object implementations by bundling information associated with a support entity and information required to instantiate a new default instance is provided. Metadata associated with the definition of the support entity indicates if a default implementation exists and includes information associated with the creation of the default implementation. The metadata of the support entity is analyzed to automatically create and return a default implementation if the provider does not supply a specific implementation.

DDEX (data designer extensibility) default object implementations for software development processes

A method for automatically retrieving source code during software debugging sessions using a development system includes stopping in an object with compiled code where the compiled code is associated with corresponding source code via a debugging support file. The compiled code can be run on different hosts. During a debugging session, a local debugger portion of the software in the development system requests a unique resource locator for the source code. A remote software debugger portion on a host responds by providing a hosttype, which specifies the host specific search algorithm, and the original path for the source code. A development system host access component requests a file with matching name and original path from the host. An original source file checksum is compared with a retrieved checksum. Upon a match, the retrieved source code is stored in the development system and accessed for user display.

Growing community of inventors

Seattle, WA, United States of America

Stephen Wharton Provine