Microsoft Technology Licensing, LLC

Michael Grier

Christopher G Kaler

Martyn S Lovell

Srivatsan Parthasarathy

Steven J Kruy

David J D'Souza

Sanjay G Shenoy

RoseMarie FitzSimons

Robert M Fries

Ashvinkumar J Sanghvi

Bradley Bartz

Alan C Shi

Aravind Ramarathinam

Micheal Dunn

Arun Upadhyaya Kishan

James Morris Alkove

Alexandre Vicktorovich Grigorovitch

Kirt A Debique

Geoffrey T Dunbar

Chadd B Knowlton

Jonathan D Schwartz

Adil Ahmed Sherwani

Sumedh N Barde

Ming Ma

Raj Jhanwar

Reid Joseph Kuhn

Michael James Day

Peter M Wilson

Vijayachandran Jayaseelan

Chaitanya Dutt Upadhyay

Michael Dunn

Brian McNeill

A logical communication path is provided between a target virtual machine (VM) and a host or application communicating with the VM. The target VM runs on a hypervisor host that has a hypervisor and a proxy agent. The hypervisor manages execution of the VM. A mapping is maintained indicating which VMs execute on which hosts. When the host or application is to send a message or packet to the target VM, the mapping is consulted and the hypervisor host hosting the target VM is identified. The message or packet, which may identify the target VM, is transmitted to the hypervisor host. A proxy agent at the hypervisor host selects a communication channel between the hypervisor and the target VM. The hypervisor then passes the message or packet through the selected channel to the target VM.

Host enabled management channel

A method of establishing a protected environment within a computing device including validating a kernel component loaded into a kernel of the computing device, establishing a security state for the kernel based on the validation, creating a secure process and loading a software component into the secure process, periodically checking the security state of the kernel, and notifying the secure process when the security state of the kernel has changed.

Protected computing environment

A software-development system or versioning system has a collection of modules for performing individual development functions such as document editing, keyword processing, and private-copy management. Each module has an interface compatible with that of the others, so that modules can be added to or substituted for the original modules, if the new modules conform to the interface. The architecture of this system supports the performance of development actions such as document merging and keyword expansion at any location within the system. The system operates upon documents and files as objects in an object space, rather than in name spaces.

Extensible architecture for project development systems

A componentization schema representing files from which an operating system or other software product is built. According to the schema, a component object represents one or more of the files. The component object has a manifest that identifies the component and specifies any dependencies between the component and other objects. Grouping objects according to the dependencies specified in manifests permits building the software product. A feature object defined by at least one component object represents a feature of the software product and a product object defined by at least one feature object represents the software product.

Software componentization for building a software product

A configuration management system creates () each configuration by assigning a configuration identifier to each configuration. In addition, relational information is computed () that indicates the relationships between the configuration and any configurations upon which it is based. The system then tracks () changes to files of the configuration by storing information associating each new file version with the configuration identifier. The system also tracks () changes to file properties. A configuration is then reconstructed () as of a desired date, by identifying () the file versions and properties associated with that configuration as of the desired date. A determination is made () whether a user that has requested the file versions has access privileges by first checking a security cache () for the user privileges information. If the information is not on the cache, it is computed from a security table () and stored on the cache. The system automatically compresses () and reconstitutes () file versions that are stored in the version store.

Project-based configuration management method and apparatus

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

A method, system and infrastructure that allow an application to run with specified versions of assemblies bound thereto, while allowing the application author, assembly publisher and/or an administrator to change the originally-specified version as desired. 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 manifest specifies any desired assembly versions, which may be redirected to another version (overridden) by an application configuration. A publisher configuration provided by an assembly publisher can similarly override the specified version. Lastly, an administrator configuration is capable of overriding other configuration versioning information. A table built from the manifest and any configuration redirection may be accessed during execution to quickly locate the appropriate version. The various configuration data structures themselves may be wrapped as assemblies, thereby enabling versioning of configurations.

Configuration for binding software assemblies to application programs

A software development system or versifying system has a collection of modules for performing individual development functions such as document editing, keyword processing, and private-copy management. Each module has an interface compatible with that of the others, so that modules can be added to or substituted for the original modules, if the new modules conform to the interface. The architecture of this system supports the performance of development actions such as document merging and keyword expansion at any location within the system. The system software interfaces to a keyword processing subsystem comprising a plurality of expanders for processing different sets of keywords and a keyword broker for selecting among the expanders, whereby the client can access resources of the software development service providers for development services identified using the keywords.

Extensible architecture for project-development systems

Configurations for binding software assemblies to application programs

A configuration management system creates ( ) each configuration by assigning a configuration identifier to each configuration. In addition, relational information is computed ( ) that indicates the relationships between the configuration and any configurations upon which it is based. The system then tracks ( ) changes to files of the configuration by storing information associating each new file version with the configuration identifier. The system also tracks ( ) changes to file properties. A configuration is then reconstructed ( ) as of a desired date, by identifying ( ) the file versions and properties associated with that configuration as of the desired date. A determination is made ( ) whether a user that has requested the file versions has access privileges by first checking a security cache ( ) for the user privileges information. If the information is not on the cache, it is computed from a security table ( ) and stored on the cache. The system automatically compresses ( ) and reconstitutes ( ) file versions that are stored in the version store.

Growing community of inventors

Woodinville, WA, United States of America

Michael Grier