Microsoft Technology Licensing, LLC

Hardik V Shah

Arshish C Kapadia

Tarkan Sevilmis

Tittu Jose

Sreekanth Lingannapeta

Maxim Lukiyanov

Gheorghita Irimescu

Janak Madhusudan Agarwal

Stephen John Clark

Jai Srinivasan

Rolando Jimenez Salgado

Mike Scavezze

Matthew James Van Gorder

Brett Ethan Johnson

Ehab Sobhy

Zlatko Michailov

John Zhongqi Wang

Alexandru Croicu

Jay R Rathi

Shaofeng Zhu

Robert Ion Gavrila

Jay Thaler

Holly A Hirzel

Hailei Zhang

Thomas Alexander Morrison

Felix Livni

Hoe Jin Kim

Chae Seong Lim

Sudheer Maremanda

Michael J Saunders

Nicholas Weinandt

Abhimanyu Sharma

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

When a software component is starting, such as but not limited to a task or a subtask, the component pushes its identification (ID) onto a stack. The component executes its other instructions. If the component completes its instructions so that it can terminate normally, it pops the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, it will not be able to pop the stack so its ID will remain in the stack. Another software process can read the IDs in the stack to identify which components have failed and can automatically take a specified action, such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Failure mode identification and reporting

When a software component is starting (), such as but not limited to a task or a subtask, the component pushes () its identification (ID) onto a stack. The component then executes () its other instructions. If the component completes its instructions so that it can terminate normally (), then it pops () the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify () which components have failed and can automatically take a specified action (), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Dynamic role selection of players for different roles in multiplayer gaming sessions is provided. Users seeking to participate in different roles in the game may request participation in the role. Selection of players for roles is made dynamically by varying a selection component for different sessions of the game. The selection component may be a user's game score over different time periods, and can be rotated for different sessions of the game, so that various levels of players have an opportunity to fill game roles.

Role assignment in multiplayer games

Growing community of inventors

Seattle, WA, United States of America

Hardik V Shah