Microsoft Technology Licensing, LLC

Haroon Ahmed

Donald F Box

Randy S Kimmerly

Robert M Bruckner

David G Campbell

David Paul Hill

Chris L Anderson

James D Laflen

Patrick McKay

Antony S Williams

John David Doty

Anthony Christopher Bloesch

Arye Gittelman

Gunter Leeb

William A Manis

Steve Antoch

Lonny Bastien

Henricus Johannes Maria Meijer

Stephen James Millet

Bradford H Lovering

Avner Y Aharoni

Brad Olenick

Laurent Mollicone

Todd F Pfleiger

Pedram Faghihi Rezaei

Fabian Omar Winternitz

Yoav Yassour

Boaz Chen

Aditya Unnithan

William Emeric Aitken

Simon David Kent

Craig Allen Lee

Noaa Avital

Andriy Garbuzov

Yury Berezansky

Quetzal Bradley

Dmitry Datsenko

Vit Karas

Oz Evren

Sadik Gokhan Caglar

A drift condition, or change, in a data structure can be detected and communicated to one or more subscribers. Data structure can be monitored by periodic configurable polling of a data source or on demand polling. Upon detection of a change in the in the data structure, subscribers can be notified of the change and optionally other information such as the identity of the object that changed and nature of the change.

Drift detection and notification

Various technologies pertaining to modifying visualizations are described herein. A client computing device requests a visualization from a server computing device, and the server computing device constructs the visualization responsive to receipt of the request. The server computing device further identifies anticipated transformations for the visualization, and transmits the visualization and the transformations to the client computing device. The client computing device displays the visualization, and responsive to receipt of a request to modify the visualization, executes a transformation provided by the server computing device to update the visualization.

Pre-fetch cache for visualization modification

The subject disclosure relates to a method and system for packaging a post-processed definition of a programming module. Contents of a constraint-based and/or order-independent execution model are received, in which the contents include a declarative source code. The contents are stored into an extensible storage abstraction such that the source code is stored in a declarative format. Metadata describing attributes of the contents stored in the extensible storage abstraction is also defined. A file is then created, which includes the extensible storage abstraction and the metadata.

Packaging system to facilitate declarative model-driven development

Embodiments render on a second data processing system, a result derived from a set of data by performing data processing across the first data processing system and a second data processing system. The amount of processing performed by the second data processing system can be dynamically adjusted. The first data processing system receives information indicating an amount of interface characteristics of the first data processing system as compared to interface characteristics of the second data processing system to be presented to a user. Data processing is dynamically allocated between the first data processing system and the second data processing system, based on an amount of interface characteristics of the first data processing system as compared to interface characteristics of the second data processing system to be presented to a user.

Dynamically adjusting brand and platform interface elements

A method includes acts for a method of rendering a result derived from a set of data by performing data processing across first and second data processing systems. The amount of processing performed by the second data processing system can be dynamically adjusted depending on business factors. The first data processing system receives information defining how the result will be rendered. The first data processing system receives information indicating at least one business constraints affecting at least one of the first data processing system or the second data processing system. The first data processing system determines data processing needed for providing the result. The first data processing system dynamically allocates the needed data processing between the first data processing system and the second data processing system, based on the business constraints affecting at least one of the first data processing system or the second data processing system.

Division of processing between systems based on business constraints

A method includes acts for rendering, on a data processing system, a result derived from a set of data by performing data processing across a first data processing system and a second data processing system. The amount of processing performed by the second data processing system can be dynamically adjusted depending on factors affecting the second data processing system. The first data processing system receives information defining how the result will be rendered at the second data processing system. The first data processing system receives information indicating factors affecting the second data processing system. The first data processing system dynamically allocates the needed data processing between the first data processing system and the second data processing system, based on factors affecting the second data processing system.

Division of processing between systems based on external factors

The subject disclosure relates to a method and system for synchronizing a repository with a declarative definition. The method and system includes receiving the declarative definition in which the declarative definition represents a constraint-based execution model. A script is also created that translates the declarative definition into machine code. At least one function is then performed on the repository in which the script provides instructions for the at least one function.

System and method for synchronizing a repository with a declarative defintion

A single software project in an integrated development environment (IDE) may be built for multiple target environments in a single build episode. Multiple different output artifacts may be generated by the build process for each of the target environments. The output artifacts are then deployed to the target environments, which may be homogeneous or heterogeneous environments. The same source project may be used to generate multiple output artifacts for the same target environment.

Simultaneously targeting multiple homogeneous and heterogeneous runtime environments

A telemetry system can parse and transform one or more change sets from a format intended to be processed by a computer to a form that is readily consumable by a human. The report or display generated to present the results can be customized for a particular domain.

Transformation of a system change set from machine-consumable form to a form that is readily consumable by a human

Data is accessed and updated in a data store at a field granularity. A user query specifies one or more non-unique fields of a record. The query is sent to a data store to retrieve the fields of the record at a field granularity, in satisfaction of the query. The fields of the record can also be modified by transmitting a record ID along with original content, while omitting some of the record data, and by also including the modification to be made.

Data framework to enable rich processing of data from any arbitrary data source

A solution authoring tool that includes an authoring environment that allows for the authoring of multiple projects of a solution including a database project that has a schema and a partner project that has a reference to the schema. When the database project is built and deployed, the database schema is made ready for runtime. When the partner project is built and deployed, the schema reference is provided within the partner software such that the partner software may interface with the database schema at runtime. To reduce or eliminate database schema drift at development time causing runtime errors at runtime, a model bus at least partially synchronizes changes made to the schema in the database project to the schema reference in the partner project, and vice versa.

Synchronizing database projects with partner projects

Changes are managed in a multi-user database application environment. Proposed changes are collected, including changes to data, schema, and/or application descriptions. A user may specify foreign key relationships between items belonging to one or more of these categories. A view is produced showing the impact proposed changes would have on the environment if successfully committed. The user's proposed changes are ordered according to their dependencies, and submitted for committal together in a single transaction, subject to optimistic concurrency and consistency checks. For example, a proposed change to a data value may be inconsistent with a change which removed a data element containing the data value. The commitment operation may return identifiers and other return values, in addition to indicating whether the commitment was successful.

Unified concurrent changes to data, schema, and application

Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Generic editor for databases

Growing community of inventors

Bellevue, WA, United States of America

Haroon Ahmed