Microsoft Technology Licensing, LLC

Adam D Stritzel

Eric P Traut

Suyash Sinha

John Michael Sheehan

Ravisankar V Pudipeddi

Tahsin Erdogan

Jason Ghssane Salameh

Adriaan W Canter

Chin Hung Lam

Christopher D Russell

Abolade Gbadegesin

Nigel Stuart Keam

Richard Bruce Ward

John E Brezak

David Allison Bennett

Adam M Smith

Jose Bernabeu-Auban

Mark Robbin Brown

Jonathan David Wiswall

Dattatraya B Rajpure

Patrick Jakubowski

Timothy Daniel Noonan

Kunal Gandhi

Howard S Kapustein

Darryl E Havens

Ciprian Gociman

Logananth Seetharaman

Andres Carlo Petralli

Jeremy B Gup

Joerg Christof Zender

William L Cheng

Jude Jacob Kavalam

Phillip E Smith

Kevin M Kieselbach

Muhammad Usman Anwer

Valeriy V Tsuryk

Daniel Ryan Mitchell

Jill Cary Bender

Denise Su-Li Goh

Fan Xiao

Adam Demont Braden

Tanaka Francis Jimha

Sarita Gupta

Nicholas Malaguti

John R Schmeichel

Kelly W Connell

Howard Scott Kapustein

Kevin Marc Kieselbach

The present disclosure concerns methods and systems for registering dynamically created packaged applications with an operating system. A dynamically created packaged application may not include a way to authenticate the packaged application but may declare a dependency on a host package. The host package may include a verified signature and be registered with the operating system. The host package may include a host runtime that references an executable included in the host package. The packaged application may not include executable files but may reference the host runtime. The operating system may register the packaged application based in part on its dependency on the host package. When the packaged application is activated, the packaged application may invoke the host runtime and the executable but do so with an application identity of the packaged application. The application identity may be different from a host runtime identity of the host runtime.

Registration of dynamically created packaged applications

Techniques for multiuser application platform are described. Generally, a multiuser application allow interaction by multiple different users with a single executing instance of the application. Implementations include a multiuser operating system and a multiuser application programming interface that enable interaction by multiple users with an executing instance of a multiuser application.

Multiuser application platform

Registration of an application in a per-user registration model includes the creation and storage of duplicate registration data for multiple user accounts present on a system. This duplication of registration data may be reduced by storing at least a portion of identical data in a per-machine location in the system memory where it is accessible to all user accounts. Instead of needing to separately re-compute and/or re-store duplicate registration data in multiple per-user locations in the memory, each user account may access and utilize the registration data stored in the per-machine location. Pre-computing and storing a portion of the application registration data in a per-machine location in the memory may also allow the system to defer the registration of the application.

De-duplication of per-user registration data

Mechanisms for synchronizing an object set with a remote data store are often performed at a particular frequency, e.g., once per hour or day. However, the objects of the object set may have different priorities, and it may be advantageous to synchronize higher-priority objects more often than regular-priority objects. The synchronization mechanisms may also differ (e.g., high-priority object synchronization may be direct and/or holistic, while regular-priority object synchronization may be differential, cached, and/or involving version and/or conflict resolution). Additionally, a resource-based threshold may be applied to the high-priority objects (e.g., a bandwidth cap) in order to reduce resource exhaustion, and high-priority objects that are not synchronized within the threshold may be synchronized with the regular-priority objects. These techniques may be particularly advantageous for synchronizing objects comprising an application state of applications of current or recent usage by a user, where application state 'staleness' is acutely visible to the user.

Opportunistic, priority-based object synchronization

A request is received from a software component of a software product to access a value of a public setting of the software component. A check is made as to whether the request conforms to an appropriate format for the public setting. If the request conforms to the appropriate format, then the requested access is performed. However, if the request does not conform to the appropriate format, then the requested access is denied. Multiple values for the public setting can be received and maintained concurrently.

Controlling access to software component state

One or more extension registrations are received for each of multiple software components installed on a computing device. The one or more extension registrations identify the software components as providers of functionality. A record of the one or more extension registrations for each of the multiple software components is maintained. Requests are received, from other software components installed on the computing device, that identify particular functionality. In response to such requests, the information regarding one or more of the multiple software components that provide the particular functionality is returned to the other software components.

Managed system extensibility

Multiple software component identifiers are maintained in a catalog of an operating system running on a device. Each of these software component identifiers corresponds to one of multiple software components installed on the device. The catalog is accessed in response to a request regarding one of the multiple software components, and the request is responded to based at least in part on information included in the catalog. Additionally, two or more versions of a software component that are installed on the computing device can be identified. Which one of the two or more versions of the software component is an active version of the software component to be run is determined. In response to requests for information regarding the software component, information regarding the active version of the software component is returned.

Catalog-based software component management

Monitoring interactions between application programs and data stores for analyzing stability of application programs. A method of the invention intercepts interactions from a plurality of application programs to a data store. The method also identifies pre-execution data relating to each of the intercepted interactions and the intercepted interaction is executed. The method identifies post-execution data relating to each of the executed interactions. The identified pre-execution data and the identified post-execution data from each of the interactions are normalized to create normalized interaction data for each of the interactions. The method combines the normalized interaction data for each of the interactions as a function of the application programs associated with each of the interactions. The method further stores the combined interaction data for analysis of the interactions between the application programs and the data store which is indicative of the stability of the application programs.

System and method for monitoring interactions between application programs and data stores

Growing community of inventors

Redmond, WA, United States of America

Adam D Stritzel