Tassaduq H Basu

20130024929, Jan 24, 2013

Jul 20, 2011

13/186474

SAJI ABRAHAM - Kirkland WA, US
Hart Wilson - Auburn WA, US
Tassaduq Basu - Redmond WA, US
Sermet Iskin - Bellevue WA, US
Liang Zhao - Bothell WA, US

Microsoft Corporation - Redmond WA

G06F 21/00

726 16

An isolation execution environment provides an application with limited resources to execute an application. The application may require access to secured resources associated with a particular trust level that are outside of the isolation execution environment. A trust activation engine determines the trust level associated with a request for a resource and operates differently based on the trust level. A broker process may be used to execute components providing access to resources having a partial trust level in an execution environment that is separate from the isolation execution environment.

20130042258, Feb 14, 2013

Aug 11, 2011

13/207806

Brent E. Rector - Redmond WA, US
Elliot H. Omiya - Kirkland WA, US
Jerry J. Dunietz - Seattle WA, US
Martyn S. Lovell - Seattle WA, US
Ales Holecek - Kirkland WA, US
Mahesh Prakriya - Redmond WA, US
Stephen C. Rowe - Bellevue WA, US
James F. Springfield - Woodinville WA, US
Noel R. Cross - Seattle WA, US
Tassaduq H. Basu - Redmond WA, US
Patrick H. Dussud - Redmond WA, US
Raja Krishnaswamy - Redmond WA, US
Steven Edward Lucco - Bellevue WA, US

Microsoft Corporation - Redmond WA

G06F 9/46

719328

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.

20130055285, Feb 28, 2013

Aug 26, 2011

13/218475

Matthew Merry - Bellevue WA, US
Hart Wilson - Auburn WA, US
Mohammad Almalkawi - Bellevue WA, US
Pierre-Yves Santerre - Bellevue WA, US
Sriram Sarda - Redmond WA, US
Tassaduq Basu - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 9/46

719313

The operating system of a computer maintains an extension catalog that stores data relating extensions with information about the contracts the extensions support. Extensions are registered in this catalog according to the contract they implement. The extension catalog can be queried to identify extensions that support a given contract. An extension can be selected from among the results from a query, and the selected extension can be activated. When activated, the extension is set up by the operating system as an independent process from, and with context from, the application for which it is an extension. Information about the extension is provided to the application to enable the extension and the application to communicate according to the supported contract.

20130055291, Feb 28, 2013

Aug 31, 2011

13/223291

Harold Pierson - Redmond WA, US
Brent Rector - Redmond WA, US
Martyn Lovell - Seattle WA, US
Mahesh Prakriya - Redmond WA, US
Stephen Rowe - Bellevue WA, US
Tassaduq Basu - Redmond WA, US
Robert A. Wlodarczyk - Issaquah WA, US
Elliot H. Omiya - Kirkland WA, US
Jerry Dunietz - Seattle WA, US
Ales Holecek - Kirkland WA, US
Lawrence W. Osterman - Woodinville WA, US
Wei Zeng - Sammamish WA, US
Neeraj Wadhwa - Kirkland WA, US
Shakeel Solkar - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 9/44

719328

Native operating system application programming interfaces (API's) are described using metadata and such descriptions are stored in a standard file format in a known location. By storing API definitions using such metadata, other applications can readily identify and use the APIs. To create such API representations, during development, a developer describes the shape of the API, including (but not limited to) the classes, interfaces, methods, properties, events, parameters, structures and enumerated types defined by the API. This API description is processed by a tool which generates a machine-readable metadata file. The machine-readable metadata file contains the same information as the API description, however in a format designed to be machine read rather than human authored.

20130055292, Feb 28, 2013

Aug 31, 2011

13/223296

Harold Pierson - Redmond WA, US
Brent Rector - Redmond WA, US
Martyn Lovell - Seattle WA, US
Mahesh Prakriya - Redmond WA, US
Stephen Rowe - Bellevue WA, US
Tassaduq Basu - Redmond WA, US
Robert A. Wlodarczyk - Issaquah WA, US
Elliot H. Omiya - Kirkland WA, US
Jerry Dunietz - Seattle WA, US
Ales Holecek - Kirkland WA, US
Lawrence W. Osterman - Woodinville WA, US
Wei Zeng - Sammamish WA, US
Neeraj Wadhwa - Kirkland WA, US
Shakeel Solkar - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 9/54

719328

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.

20130066899, Mar 14, 2013

Sep 10, 2011

13/229697

Lawrence W. Osterman - Woodinville WA, US
Harold L. Pierson - Redmond WA, US
Elliot H. Omiya - Kirkland WA, US
Martyn S. Lovell - Seattle WA, US
Mahesh Prakriya - Redmond WA, US
Stephen C. Rowe - Bellevue WA, US
Tassaduq H. Basu - Redmond WA, US
Robert A. Wlodarczyk - Issaquah WA, US
Wei Zeng - Sammamish WA, US
Neeraj N. Wadhwa - Kirkland WA, US
Shakeel I. Solkar - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707769, 707E17014

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.

20160110229, Apr 21, 2016

Oct 16, 2014

14/515516

- Redmond WA, US
Lawrence William Osterman - Woodinville WA, US
Tassaduq Basu - Sammamish WA, US

G06F 9/54
G06F 9/48

Technologies for a contract platform versioned according to the set of API contracts provided. API contracts are both development-time and run-time executable components. Each such contract defines a particular set of APIs that are fully supported at run-time by a corresponding implementation module. Contract applications are written to API contracts as opposed to the monolithic APIs of a legacy platform. Such applications are “platform agnostic”.

20150106915, Apr 16, 2015

Nov 30, 2014

14/556221

- REDMOND WA, US
HART WILSON - AUBURN WA, US
TASSADUQ BASU - REDMOND WA, US
SERMET ISKIN - BELLEVUE WA, US
LIANG ZHAO - BOTHELL WA, US

G06F 21/60

726 16

An isolation execution environment provides an application with limited resources to execute an application. The application may require access to secured resources associated with a particular trust level that are outside of the isolation execution environment. A trust activation engine determines the trust level associated with a request for a resource and operates differently based on the trust level. A broker process may be used to execute components providing access to resources having a partial trust level in an execution environment that is separate from the isolation execution environment.