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

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

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

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

Abstract: A collaboration database service allows end users to create and collaborate on custom databases as any other type of productivity content (presentations, word processing documents, spreadsheets, etc.). Providing a more data centric experience rather than formatting centric may allow for a malleable experience. The custom entities the user defines may indicate how to best display the data on various devices, what rules should be enforced, and what actions need to be taken on behalf of the user. A collaboration database service according to embodiments may not only provide easy creation and sharing of various databases across devices, but also integrate and interoperate with various productivity application workloads. Each productivity application may play a unique role, and those individual strengths may be highlighted in an example service to bring the system together.

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

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

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