Abstract: A computer system, comprising one or more processors and a memory including instructions that, when executed, cause the one or more processors to at least: execute a first executable application; access a first registration request from a second executable application; validate a digital certification of the one or more components of the second executable; in response to the validating of the digital certification of the one or more components, save information from the first registration request into a registration store, wherein the information saved from the first registration request includes a unique identifier including (1) an identification of one or more types of events, and (2) a package family name; and send a raised event without requiring further authentication from the second executable application.

Abstract: A computer system, comprising one or more processors and a memory including instructions that, when executed, cause the one or more processors to at least: execute a first executable application; access a first registration request from a second executable application; validate a digital certification of the one or more components of the second executable; in response to the validating of the digital certification of the one or more components, save information from the first registration request into a registration store, wherein the information saved from the first registration request includes a unique identifier including (1) an identification of one or more types of events, and (2) a package family name; and send a raised event without requiring further authentication from the second executable application.

Abstract: An example method includes executing a first executable application designed for execution using a first application programming interface (API). A first registration request is accessed from a second executable application designed for execution using a second API different from the first API, the first API and the second API executed within a same operating system environment. In response to validating of a digital certification of the second application, information from the first registration request is saved into a registration store. An event is raised having an event type and event information, and in response to determining that an event type of the raised event is saved in the registration store, the raised event is sent without requiring further authentication from the second executable application.

Abstract: There are presently no solutions that address Universal Windows Platform (UWP) application discoverability in a secure and/or company-specific fashion. Presently, UWP applications have to be specifically designed to communicate with other UWP Apps that are not from the same vendor. Further, UWP App Services currently have no Windows-native registration or discoverability paradigms. Typically, for UWP-to-UWP communication (for which App Services are typically used), the attempted connection to an App Service would be the first point of discoverability. The solutions presented herein eliminate the need to have any pre-arranged dependencies between the UWP application's author and the Win32 Desktop Application's author, e.g., in instances when the Win32 application needs a coded awareness of the supported UWP application's App Services.