Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.