Microsoft Technology Licensing, LLC

Mahesh Prakriya

Christopher Wellington Brumme

Martyn S Lovell

Elliot H Omiya

Stephen C Rowe

Tassaduq Basu

Wei Zeng

Patrick Henri Dussud

Sean Edwin Trowbridge

Brian M Grunkemeyer

Lawrence William Osterman

Robert Albert Wlodarczyk

Michael Aksionkin

Shakeel Solkar

Neeraj Wadhwa

Jerry Jay Dunietz

Ales Holecek

Brent Rector

WeiWen Liu

Raja Krishnaswamy

Rudi Martin

Ian H Carmichael

Harold L Pierson, Iii

Steven E Lucco

Gregory Darrell Fee

Sebastian Lange

Noel Richard Cross

James F Springfield

Shoshanna K Budzianowski

Harold Pierson

Vance Palmer Morrison

Christopher David Brown

Beysim Sezgin

Peter Alan Carlin

Alan C Shi

David S Mortenson

Steven J Pratschner

Suzanne Maurine Cook

Mason K Bendixen

Mei-Chin Tsai

Simon Jeremy Hall

Dario Russi

Xiaoning Ling

Michael Gashler

Sonja Keserovic

Brian F Sullivan

Robin M Maffeo

Xiaoing Ling

Tassaduq H Basu

Steven Edward Lucco

Brent E Rector

Lawrence W Osterman

Various embodiments provide an ability to describe, independent of a programming language, one or more interfaces associated with an operating system. Alternately or additionally, a compiler associated with a specific programming language can be configured to map the independent interface description(s) to the specific programming language. In some embodiments, an application can be configured to programmatically determine one or more interfaces of the operating system.

Runtime system

Information about the operating system application programming interfaces is stored in a known format in a known location. This information fully describes the APIs exposed by the operating system and is stored in API metadata files. A language compiler or interpreter uses this API information to build a natural and familiar representation of the native system API in the target language. The language compiler or interpreter can read the API information at compile time and/or runtime. The metadata is used to allow an application to refer to named elements in the API. Projections are built that use the metadata to map named elements in the API to named elements in the target language, and to define wrappers that marshal data of those elements between the target representation and the native operating system representation.

Projecting native application programming interfaces of an operating system into other programming languages

Various embodiments provide an ability to abstract type resolution between multiple type systems. At least one type can be described in one or more programmatically accessible file(s). In some embodiments, an application using a different type system can programmatically access and resolve a type of the at least one type system without knowledge of a location of where a description of the type resides. Alternately or additionally, type descriptions contained in the one or more programmatically accessible file(s) can be analyzed and restructured into one or more new programmatically accessible file(s) based, at least in part, upon the type descriptions.

Flexible metadata composition

Dynamic memory management configuration enables certain behavior of an application to be controlled without touching or affecting any executable portion of the application.

Memory management configuration

A host intercepts calls between two executables and determines whether the calls are permissible according to the host's security model which can be identify based, such as user identity based&#x2014;for instance, mapping access rights within a specific data base user context to database object access. Such an identity security model differs from a common language runtime security model where managed code uses Code Access Security to prevent managed assemblies from performing certain operations. Managed assemblies registered with the host are host objects from the host's perspective for which access rights can be defined via security rules, such as are defined for individual user identities. A host can decide access between managed executables based on the host's identity based access rules by trapping any cross assembly calls and deciding whether such calls should proceed or be blocked from taking place based on the corresponding identity security settings.

Cross assembly call interception

Authored code may include a notification that no tolerance for failure or corruption is expected for an identified sub-set of the code. Any potential failure point, which may be induced by a runtime environment routine or sub-routine, that is associated with the identified sub-set of code may then be identified and hoisted to a point apart from the identified sub-set of code.

Constrained execution regions

A host operating in a managed environment intercepts a call from a managed caller to a particular callee and determines whether the call is permissible according to the host's prior configuration of a plurality of callees. The particular callee, which provides access to a resource that the host can be protecting, can have been previously configured by the host to always allow the call to be made, to never allow the call to be made, or to allow the call to be made based upon the degree to which the host trusts the managed caller.

Hosted code runtime protection

A finalizer may include a notification that no tolerance for failure or corruption is expected. Any potential failure point, which may be induced by a runtime execution environment routine or subroutine that is associated with the finalizer may then be prepared apart from the finalizer.

Critical finalizers

Enabling secure and efficient marshaling, utilization, and releasing of handles in either of an operating system or runtime environment includes wrapping a handle with a counter to tabulate a number of threads using currently using the handle. Thus, handle administration is implemented to circumvent potential security risks, avoid correctness problems, and foster more efficient handle releasing.

Safe handle

Reliability contracts declare an intent of executable code, and may be associated with at least a portion of the executable code. The intent of the executable code in the face of particular conditions may be declared for the use in any one of a programming, execution, or testing environment.

Reliability contracts

Deterministic code execution may be recovered for programs or portions thereof by implementing a programmable policy on a system host to escalate the scope of a code discard based on various parameters.

Execution recovery escalation policy

Growing community of inventors

Redmond, WA, United States of America

Mahesh Prakriya