Microsoft Technology Licensing, LLC

Sanjay G Shenoy

David J D'Souza

Srivatsan Parthasarathy

Michael Grier

RoseMarie FitzSimons

Alan C Shi

Micheal Dunn

Loren Kohnfelder

Ryan M Burkhardt

Donald McNamara

Cem Paya

Louis Lafreniere

Ray Sun

Eric Robert Berman

Sean L Flynn

Tom G Yaryan

Seung-Yup Chai

Eric J Hennings

Peter M Wilson

Seetharaman Harikrishnnan

Michael J Wallent

Michael Dunn

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 componentized operating system is separated into multiple different components. In certain embodiments, a bill of materials (BOM) identifies at least one component that is installed (or is to be installed) for an operating system image on a computer. Each component includes one or more files and has a corresponding manifest that identifies which other components (if any) the component is dependent on. During an installation or upgrading process, the manifest for a component can be accessed to determine which additional components (if any) are to be installed even if they are not explicitly identified in the BOM.

Componentized operating system

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 method, apparatus, and article of manufacture for detecting and preventing input data buffer overrun storing a security token containing a randomly generated data pattern in memory between an input data buffer and memory locations containing instruction address pointers. First one pushes all arguments to a function onto the stack data structure and pushes a return address onto the stack data structure for use in obtaining the memory address for the instruction to be executed upon completion of the function before it pushes onto the stack data structure a security token. This security token comprises a randomly generated data value. Next one allocates memory locations on the stack data structure for use as local variables within the function, completes the instructions within the function, retrieves the security token value from the stack data structure; and if the retrieved security token value is identical to the randomly generated data value, returns from the function using the return address stored on the stack data structure.

Input buffer overrun checking and prevention

Configurations for binding software assemblies to application programs

A system and method of saving a Web page from a Web site on an Internet to a computer-readable medium is disclosed. A Web page is downloaded from the Internet to the computer-readable medium. The Internet address for the Web page is stored on the computer-readable medium. When the Web page is opened from the computer-readable medium, the Internet address is used to identify a security context for the Web page. By using the Internet address to identify the security context for the Web page, the system and method of the present invention allows users to securely view and execute Web pages downloaded from the Internet.

Saved Web page security system and method

Growing community of inventors

Redmond, WA, United States of America

Sanjay G Shenoy