Microsoft Technology Licensing, LLC

Gabriel J Hall

Mauricio Ordonez

Alan Aitken Ramaley

Xiao Wu

Jay R Rathi

Dorrene Elizabeth Brown

Shreedhar Thirugnanasambantham

Taesuk Yoon

John Zhongqi Wang

Joey Masterson

Sreekanth Lingannapeta

Seung Wook Son

Nate Waddoups

Darren Miller

Ela Malani

JongHwa Lim

Chetan Dandekar

Brian M Jones

Rolando Jimenez Salgado

Yi Li

William James Griffin

Krista Bendig

Phillip David Allen

Humberto Lezama Guadarrama

James Richard Sturms

Richard Eric Andeen

Dmitry Pugachev

Robert Charles Ward

Eilene Hao

Alexander Malck

Jeremy Michael Ehrhardt

Applications may be created and registered to an online ecosystem and then execute within individual web applications such as productivity applications, communication applications, collaboration applications, and so on. These non-native applications may be enabled to interact with files and provide custom experiences for a user. The applications may also be enabled to interact with additional information discovered about the user within the ecosystem to provide custom experiences. The applications may further be enabled to create custom workflows to allow users to accomplish new tasks.

Support for non-native file types in web application environment

A consumer oriented data service is provided. A data collaboration service initiates operations to provide access to data from multiple sources by managing a data table of aggregate data fields based on a request from a client application. The request includes a consumer identification and data queries. An ownership of the data table is assigned based on the consumer identification. Local data fields identified in the data queries are inserted into the data table and populated with local datasets stored in the queries. External data fields identified in the data queries are inserted into the data table and populated with links to external datasets stored in external data sources.

Provide consumer oriented data service

A method for providing client application integration for workflow management includes receiving a verification file, accessing a file through a client application, determining, based on the verification file, whether the accessed file includes a reference to a workflow component of a workflow stored on a server, retrieving the workflow component from the server, and displaying the workflow component referenced by the accessed file via an in-line user interface of the client application, further including displaying at least one selectable workflow management option for managing the workflow component using the client application.

Client application integration for workflows

An interface mechanism is provided for developers to bundle together a set of extensions (or add-ins) to a productivity suite allowing end users and system administrators to manage their lifecycle in a unified way. Aspects such as discovery, acquisition, authorization deployment, management, updates, and similar ones may be addressed for the bundle as opposed to each of the different extensions (for example extensions for different versions of the same application such as desktop version, web application version, mobile version, etc.). Bundles may also provide a means to match specific functional sets or commercial offerings to specific user or customer profiles.

Extensibility bundles for a cloud and devices suite

A front-end computing system initializes an instance of a workflow. The workflow contains a plurality of activities. The plurality of activities includes a shim activity. When the front-end computing system executes the workflow instance, the front-end computing system performs the shim activity. When the front-end computing system performs the shim activity, the front-end computing system sends a custom activity assembly to a sandbox computing system. The custom activity assembly is not fully trusted. The sandbox computing system executes the custom activity assembly. The sandbox computing system is isolated from the front-end computing system such that unexpected behavior of the sandbox computing system does not cause the front-end computing system to perform unexpected behavior.

Implementing custom activities in a workflow

A method for packing the multiple files and folders of an HTML Web page into a single MHTML file. The packing process begins by determining whether the user has write privileges to the current location. If not, the user is prompted to save the MHTML file in an alternate location (e.g., the desktop). If the user has write privileges to the current location, the process opens the main HTML Web page and searches for supporting resource files. In short, the supporting resource files are identified by searching for known, common resource file references in the main HTML source file. When the resource file references have been identified, the process packages the main HTML document and all of the supporting resource files into a single file in MHTML format. The unpacking process opens the MHTML file and identifies the main HTML document portion, as well as the portions of the MHTML file containing the supporting resource files. Once all of the components have been identified, the Web page's folder structure is determined by referring to the content location field contained in each separate portion of the MHTML file. The individual MHTML components are converted into files and the main HTML file is stored. The resource files are stored in locations relative to the main HTML file, as identified by the unpacked folder structure.

Method and system for packing and unpacking web pages

An email client is configured to watch for attachment events and to automatically package a web page as a single-file attachment to an email note. When an attachment event is recognized by the email client, a determination is made as to whether the attached file is an HTML document. If the attached document is an HTML document, then a determination is made as to whether the HTML document has supporting resource files. If the HTML file has supporting resource files, then the registry is checked to see if the user has specified to include all supporting resource files with any HTML attachment. If not, then the user is prompted by a dialog box to select whether the supporting resource files should be attached. If the user expresses a desire to have the supporting resource files attached then the web page and all supporting resource files are packaged into a single file in Web Archive (e.g., MHTML) format. This single file is attached to the email note and transmitted with the email note to the recipient. The recipient will be able to unpack the attachment so that the web page can be displayed in its original form.

System and method for sending a web page via electronic mail

Growing community of inventors

Woodinville, WA, United States of America

Gabriel J Hall