Microsoft Technology Licensing, LLC

Shakeel Solkar

Wei Zeng

Martyn S Lovell

Elliot H Omiya

Mahesh Prakriya

Lawrence William Osterman

Stephen C Rowe

Robert Albert Wlodarczyk

Tassaduq Basu

Michael Aksionkin

Neeraj Wadhwa

Harold L Pierson, Iii

Jerry Jay Dunietz

Ales Holecek

Brent Rector

Scott A Moody

Yuedong Yin

Harold Pierson

Kiran Nallabothula

Doru Constantin Nica

Dylan Symington

Srihari Busam

Sathish Kumar Venkat Rangam

Himanshu Misra

Minjun Wu

Svetlana A Borodina

Kevin Matthew Dargie

Jonathan H Mollerup

Ning Zhuang

Zyanya Valdes Esquivel

Luis Delgado

Diana Slaba

Lawrence W Osterman

A client computing system receives a chat message with an action identifier. The chat message is parsed to identify executable recovery code on the client computing system. The executable recovery code is represented in a chat message interface on the client computing system, along with an authorization actuator. Actuation of the authorization actuator is detected and the recovery code is executed on the client computing system.

Remote recovery and support using chat messages

A client computing system detects when a problem is encountered with an application and identified problem-specific diagnostic data that is to be collected, given the detected problem. It also identifies one or more problem-specific test or diagnostic analyzers and executes those analyzers to generate additional data. The data that is collected and the data that is generated by the analyzers is packaged and sent to a service computing system for identifying a remedial action that can be performed to address the problem. The remedial action is received and surfaced for the user.

State-based remedial action generation

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

Growing community of inventors

Sammamish, WA, United States of America

Shakeel Solkar