Harold Lewis Pierson, 54Redmond, WA

8433697, Apr 30, 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

707706, 707769

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.

2013005, 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.

2013005, 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.