Microsoft Technology Licensing, LLC

Lawrence M Sanchez

Suryanarayanan V Raman

Sarita M James

Brian J Syme

John A Licata

Zoltan Pekic

Namendra Kumar

Rolando Jimenez Salgado

Todd J Abel

David Koronthaly

Patrick Dengler

Maarten Mullender

Jagdish Singh

Ricard Roma I Dalfó

Jared R Parker

Satish Kumar Chittamuru

Thomas Gersten

Sai Shankar

Arvind Kumar Krishnan

Jeff Staiman

Nabarun Mondal

The embodiments described herein generally relate to systems and methods for providing human interaction with a business application from an email client. To complete a business process, individuals often must provide information to a business application. However, it may be difficult for the individual to interact with the application if the user is not familiar with the application's user interface (UI) or if it is necessary to navigate to the application's UI. Accordingly, it may be more efficient to interact with the application using a UI within an email client. User input for an automated business process can be submitted from a general-purpose email client. Benefits from such include providing input to a business application while working within the familiar email interface; not needing to switch contexts to complete work for the application; and completing work for the application while being offline or having limited corporate network connectivity.

Human interaction with application from email client

Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Metadata driven user interface

Methods and systems for software delivery are described. In one embodiment, an extension definition catalog structure is defined and can be used to select one or more software extensions for incorporation on a computing device. At least one software extension is identified using a uniform resource name and, for the one software extension, at least one instance of the software extension is identified using a uniform resource name. For the one instance of the software extension, a uniform resource locator can be used to select the instance.

Methods and systems for delivering software

User interfaces are defined by metadata for use with productivity suite applications in a wrapped window, a task pain, or some other suitable representation. Data can be bound to a data source in a one-way format such that changes from the data source propagate to property fields in the UI form. Data can also be bound to a data source in a two-way format such that changes from the property field of the UI propagate back to the data source. The data source can be a local cache such as for synchronization between a productivity suite application and a line of business (LOB) application (e.g., CRM applications). A rendering engine is arranged to process the UI and data bindings such that custom event handlers are defined in a code behind assembly format. Productivity suite items are accessible from the code behind assembly through a series of item interfaces.

Interfaces for a productivity suite application and a hosted user interface

Methods and systems for network-based or Internet-based software delivery are described. In one embodiment, an application program or software platform resides on a client and is configured so that it is extensible based on software extensions that are deliverable over a network such as the Internet. Various extensions can be developed by third party developers for incorporation into the program or platform.

Methods, systems, architectures and data structures for delivering software via a network

Methods and systems for network-based or Internet-based software delivery are described. In one embodiment, an application program or software platform resides on a client and is configured so that it is extensible based on software extensions that are deliverable over a network such as the Internet.

Methods and systems for delivering software via a network

Methods and systems for network-based or Internet-based software delivery are described. In one embodiment, an application program or software platform resides on a client. The program or platform is configured so that it is extensible based on software extensions that are deliverable over a network such as the Internet. Various extensions can be developed by third party developers for incorporation into the program or platform. In the described embodiment, extension files that comprise a software extension are hosted on an Internet server. Additional files are also hosted on the Internet server and describe aspects of the software extension. These additional files include files that describe a logical attachment of the extension to the program or platform, as well as files that describe the location of the extension files. Extensions are incorporated on a client by navigating to a particular Internet site through which the extensions can be accessed. The files describing the extension files are downloaded on the client. These files tell the client where the particular extension is to be plugged in, as well as where to find the appropriate extension files and how to download them. The extension files are then downloaded and incorporated into the program or platform.

Barbeque grill with tire tread pattern

Growing community of inventors

Redmond, WA, United States of America

Lawrence M Sanchez