Michael G Grier, 665467 Maple Vis, San Antonio, TX 78247

6871344, Mar 22, 2005

Apr 24, 2001

09/842278

Michael J. Grier - Woodinville WA, US
Sanjay G. Shenoy - Redmond WA, US
RoseMarie FitzSimons - Seattle WA, US
David D'Souza - Mercer Island WA, US
Srivatsan Parthasarathy - Bellevue WA, US
Micheal Dunn - Redmond WA, US
Alan Shi - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F009/45

717162

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.

6915507, Jul 5, 2005

Nov 21, 2000

09/717537

Christopher G. Kaler - Redmond WA, US
Martyn S. Lovell - Seattle WA, US
Michael J. Grier - Woodinville WA, US
Bradley J. Bartz - Lynnwood WA, US

Microsoft Corporation - Redmond WA

G06F009/44

717103

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.

6928447, Aug 9, 2005

May 21, 2004

10/850780

Christopher G. Kaler - Redmond WA, US
Steven J. Kruy - Carnation WA, US
Martyn S. Lovell - Seattle WA, US
Michael J. Grier - Woodinville WA, US

Microsoft Corporation - Redmond WA

G06F017/30

707101, 707203

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.

6973466, Dec 6, 2005

May 21, 2004

10/851945

Christopher G. Kaler - Redmond WA, US
Steven J. Kruy - Carnation WA, US
Martyn S. Lovell - Seattle WA, US
Michael J. Grier - Woodinville WA, US

Microsoft Corporation - Redmond WA

G06F017/30

707203

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.

7073170, Jul 4, 2006

Mar 21, 2005

11/085673

Michael J. Grier - Woodinville WA, US
Sanjay G. Shenoy - Redmond WA, US
RoseMarie FitzSimons - Seattle WA, US
David D'Souza - Mercer Island WA, US
Srivatsan Parthasarathy - Bellevue WA, US
Michael Dunn - Redmond WA, US
Alan Shi - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 9/44

717162, 717164, 717167

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.

7251655, Jul 31, 2007

May 21, 2004

10/851885

Christopher G. Kaler - Redmond WA, US
Steven J. Kruy - Carnation WA, US
Martyn S. Lovell - Seattle WA, US
Michael J. Grier - Woodinville WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707 9, 707203

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.

7287259, Oct 23, 2007

Apr 24, 2001

09/842270

Michael J. Grier - Woodinville WA, US
RoseMarie FitzSimons - Seattle WA, US
David D'Souza - Mercer Island WA, US
Peter Wilson - Kirkland WA, US
Srivatsan Parthasarathy - Bellevue WA, US
Sanjay G. Shenoy - Redmond WA, US
Micheal Dunn - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 9/44

719331, 717164

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.

7475097, Jan 6, 2009

Nov 24, 2004

10/996719

Christopher G. Kaler - Redmond WA, US
Steven J. Kruy - Carnation WA, US
Martyn S. Lovell - Seattle WA, US
Michael J. Grier - Woodinville WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707203, 707 9, 717121

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.