Microsoft Technology Licensing, LLC

Daniel Oliver

Anshul Rawat

Max Glenn Morris

Jerry K Koh

Sandy Wong

Steve Seixeiro

Robert Emmett Kolba, Jr

Sashi Raghupathy

Manoj Kumar Biswas

Michael G Sheldon

Benjamin Betz

Michael D McCormack

Amy Harilal Rambhia

Brian L McNeil

Andrew V Davidson

Christopher J Guzak

Daryl Tanghe

Relja Ivanovic

Ramkumar Ramasubramanian

Brandon H Paddock

Ramaswamy Krishnan-Chittur

Paul J Leach

Chris J Guzak

John Michael Sheehan

Sriram Srinivasan

Gaurav S Anand

Kenneth Martin Tubbs

Elliot H Omiya

Tracy Dianne Schultz

Christopher Scott Dickens

Scott E Dart

Rodger William Benson

Ryan Charles Colvin

Shajib Sadhukha

Timothy R Sullivan

Giles Edward Van Der Bogert

Elliott Jeb Haber

Ameya S Bhatawdekar

Liwei Chen

Lindsey R Noll

Robert John Anderson

Karanbir Singh

J Adrian Lannin

Ram Ramasubramanian

Shawn E Maloney

Crispin Cowan

Matthew Merry

Frank Olivier

Charles Aaron Hare

Jason R Olson

Michael David Mccormack

Melitta Lorraine Geistdoerfer Andersen Riley

Ian H Kim

Xiang Tu

James Dooley

Andy Davidson

Jay Dave

Benjamin David Langmaid Stewart

Robert Emmett Kolba

Brian Mcneil

An action framework system provides context-based actions in association with a source application. The source application detects selection of a content element presented by the source application. The content element is associated with an application identifier identifying a target application and an action identifier identifying an operation to be executed by the target application on the content element. The target application identified by the application identifier is executed to perform the operation identified by the action identifier on the content element, responsive to detection of the selection of the content element. In one implementation, the source application is a search feature providing different contexts of search results (e.g., from a local file system search, a local application content search, a Web search, a remote application content search).

Context-based actions from a source application

A search service executes on one or more computing systems and searches at least one index associated with content accessible through an application based on the at least one portion of the search query to provide search results associated with the application. A search results interface returns one or more search results from the search. At least one of the search results is associated with an application identifier identifying the application. The search service ranks the search results associated with the application with other search results from at least one other search of other content based on the search query.

Search result contexts for application launch

Schematized data roaming is described herein. In one or more implementations, a cloud service includes a cloud data store that is configured to store schematized data comprising user preferences and settings of client devices associated with a user profile. The schematized data includes a schema that is shared across the client devices and globally defined by the cloud service which enables the user preferences and setting to be re-used across multiple devices and device classes, including devices that the user has not previously interacted with before. The schematized data includes attributes, for each schematized data structure, which provide rules for processing or storing the corresponding schematized data structure in the cloud data store. Such attributes may include a conflict resolution policy, an upload policy, or a partition policy.

Schematized data roaming

Techniques for application activation are described herein. An operating system (OS) can be configured to incorporate various extension points that are serviceable through contracts defining individual invocations of extensible functionality. The extensible functionality is integrated as part of the OS and controlled by the OS in a centralized manner. However, the specific implementations of the extensible functionally are offloaded to applications using the contracts. For example, the OS can include or otherwise make use of a centralized application activation component that employs an object-oriented approach to invoke applications to perform particular contracts. The application activation component can pass information describing a particular contract to activate a designated application and enable the application to service the contract in the manner specified by the OS. In this way, the manner in which contracts are handled by application code can be managed and coordinated through a centralized application activation component.

Application activation framework

Techniques for modes for applications are described. In one or more implementations, multiple operational modes are provided for an application. The operational modes can be associated with different resource access permissions, trust statuses, graphical user interfaces, and so on. An application can be launched in a particular one of the operational modes based on a context in which a request to launch the application is received. In one or more implementations, correlations between launch request contexts for an application and operational modes can be configured to enable different launch requests to cause an application to launch into different operational modes.

Modes for applications

Method and computer storage media for sharing resources between a plurality of computing devices associated with a common non-enterprise network. A common set of credentials is stored on at least two or more of a plurality of computing devices that reside behind a routing device and are associated through a common non-enterprise network. Upon storing the common set of credentials, each of the two or more of a plurality of computing devices create a local account that contains, at least, the common set of credentials. The common set of credentials allow for the sharing, among the two or more of the plurality of computing devices, of resource that reside on or are associated with the computing devices.

Associating computing devices with common credentials

The reputation of an executable computer program is checked when a user input to a computing device initiates a program launch, thus triggering a check of a local cache of reputation information. If the local cache confirms that the program is safe, it is permitted to launch, typically without notifying the user that a reputation check has been made. If the local cache cannot confirm the safety of the program, a reputation check is made by accessing a reputation service in the cloud. If the reputation service identifies the program as safe, it returns an indication to the computing device and the program is permitted to be launched, again without notifying the user that a reputation check has been made. If the reputation service identifies the program as unsafe or potentially unsafe, or does not recognize it at all, a warning is displayed to the user.

Reputation checking of executable programs

Display screen with graphical user interface

In accordance with the automatic peripheral device sharing, a peripheral device that has been newly installed on a device is detected and is shared with one or more additional devices coupled to the device. A notification of the peripheral device is automatically published to the one or more additional devices. This notification includes an indication of how the one or more additional devices can access the peripheral device. Each of the one or more additional devices can receive this notification and determine whether the peripheral device can be automatically installed on that device without user input. For each of the one or more additional devices, the peripheral device is installed on that device only if the peripheral device can be automatically installed on that device without user input.

Automatic peripheral device sharing

Embodiments of the present invention relate to systems and methods for configuring computing devices to join a peer group. A peer group may be created on a subnetwork by a computing device. When a new computing device enters the subnetwork, it may join the peer group and be given access to the shared resources on the peer group and associated computing devices, using a communications layer and an authorization layer. Allowing a new computing device to join a peer group includes inviting the new device to join and then challenging the device for a passkey of the peer group. After joining the peer group, the computing device will be able to access and share resources with the peer group and other computing devices associated with the peer group.

Configuration of a peer group

Growing community of inventors

Seattle, WA, United States of America

Daniel Oliver