Microsoft Technology Licensing, LLC

Google Inc.

Peter M Wilson

David J D'Souza

RoseMarie FitzSimons

Seetharaman Harikrishnnan

Srivatsan Parthasarathy

Richard Allen Pletcher

Michael Grier

Kenneth Paul Fishkin

Stephen Francis Yegge

Sanjay G Shenoy

Micheal Dunn

Myung Ryul Jang

A first device captures content and streams the captured content to a second device as the first device continues to capture the content.

Content sharing

Methods, systems and data structure are described for implementing local isolated DLL and/or COM components. A version of a shared component is stored in a local directory with an application that uses that particular version. Another version of the shared component exists on the system and is useable by any number of other computer programs. A local file is created in the local directory that indicates the presence of an isolated version of the shared component. When the application calls the shared component, the system uses the isolated version of the shared component stored locally with the application program. Thus, specific versions of components may be provided to a calling application without making any code changes to the calling application or to the component to which the calling application is bound.

Method and systems for DLL/COM redirection

A method and system for providing a common operating system feature set for supporting a variety of operating system configurations is described. The common operating system feature set is organized to provide a minimal memory footprint applicable to a number of devices and methods of deployment. The common operating system includes dependencies among operating system components that provide a selection of integrated components that are validated for reliability. The common operating system includes an application program interface set that provides functionality for a variety of operating system scenarios.

Method and system for providing a common operating system

An infrastructure that allows applications to run with specified versions of dependent assemblies, wherein each assembly may exist and run side-by-side on the system with other versions of the same assembly being used by other applications. An application provides a manifest to specify any desired assembly versions on which it is dependent. Similarly, each assembly may have an assembly manifest that specifies the versions of assemblies on which it is dependent. During an initialization phase, an activation context is created for the application, based on the manifests, to map version independent names to a particular assembly version maintained on the system. While the application is in a running phase, for any globally named object that the application wants created, the activation context is accessed to locate the application's or assembly's manifest-specified version. The manifests and activation context constructed therefrom thus isolate an application from assembly version changes.

Isolating assembly versions for binding to application programs

Methods, systems and data structure are described for implementing local isolated DLL and/or COM components. A version of a shared component is stored in a local directory with an application that uses that particular version. Another version of the shared component exists on the system and is useable by any number of other computer programs. A local file is created in the local directory that indicates the presence of an isolated version of the shared component. When the application calls the shared component, the system uses the isolated version of the shared component stored locally with the application program. Thus, specific versions of components may be provided to a calling application without making any code changes to the calling application or to the Component to which the calling application is bound.

Growing community of inventors

Kirkland, WA, United States of America

Peter M Wilson