Microsoft Technology Licensing, LLC

Shaofeng Zhu

Robert McKee Howard

Eray Aydin

Michael C Fanning

Jai Srinivasan

Rolando Jimenez Salgado

Titus Constantin Miron

Venkatesh Veeraraghavan

Zhenguang Chen

William R Taylor

Charles Reeves Little, Ii

Zachary A Nation

Frederico A Mameri

Ehab Sobhy

Zlatko Michailov

John Zhongqi Wang

Alexandru Croicu

Jay R Rathi

Robert Ion Gavrila

Hardik V Shah

Tim McConnell

Hailei Zhang

Thomas Alexander Morrison

Cindy Liao

Chae Seong Lim

Hoe Jin Kim

Naganandhini Kohareswaran

Sudheer Maremanda

Michael J Saunders

Abhimanyu Sharma

Nicholas Weinandt

Jeff Crowley

Joseph C Chang

Robert Mckee Howard

Systems, methods, and computer-executable instructions for supporting custom functions within an application. An application add-in is received that includes a custom function and a custom function location. The application is available across multiple platforms. The custom function is also available across multiple platforms. The custom function is registered within the application using the custom function location. A request to invoke the custom function is received within the application A custom function implementation is downloaded from the custom function location. The custom function implementation is executed. A return value is received from the custom function implementation. The return value may be displayed within the application.

Cross platform custom functions

Disclosed herein are systems, methods, and software to enhance the interoperability of components written in different programming languages. In an implementation, a code service receives a request message communicated by an application component via a message interface in an application environment that is at a layer above a target environment. The request message includes a request to invoke a target component available in the target environment and programmed in a language different from that of the application component. In response to the request, the service identifies at least a service component associated with invoking the target component in the target environment. The service component is executed to invoke the target component via a component interface.

Code service for language-independent dispatch

An application submits a permission request to a resource server. In response to receiving the request, the resource server generates a user interface that asks the user to grant or deny the requested permissions. If the permissions are granted, data is stored indicating that the application has the requested permissions. When a runtime request for a resource is received, the resource server determines whether the request has been made by a user, by an application, or by an application on behalf of a user. If the request is made by an application only, the request is granted only if the application has permission to access the resource by way of a direct call not on behalf of a user. If the request is made by an application on behalf of a user, the request is granted only if both the user and the application have sufficient permission.

Authorizing application access to secure resources

A cross-browser dialog platform is provided for supporting hosted web pages in a dialog, such that a web page may be used inside or outside the dialog. Select elements on the hosted page may be hidden when in a dialog, different behavior may be specified for hyperlinks inside or outside the dialog, and a proper size of the dialog may be inferred from its contents without designer input.

Cross-browser web dialog platform

Remote event receivers can register with a document repository computing system to receive notifications of events occurring at a document repository. The remote event receivers may register to receive notifications synchronously, whereby the remote event receivers can provide a response to the notification prior to the occurrence of the event, or asynchronously, whereby the remote event receivers provide no response. Synchronous remote event receivers can also specify in a response to the notification that the event should be canceled or may specify properties that should be changed. Remote event receivers can be pre-event receivers that receive notifications prior to the occurrence of an event, or post-event receivers that receive notifications following the event. When an event is to occur at the document repository, notifications are provided to the pre-event remote event receivers. Once the event has occurred, notifications are provided to the post-event remote event receivers.

Providing notification of document repository events to external systems

Growing community of inventors

Bellevue, WA, United States of America

Shaofeng Zhu