Microsoft Technology Licensing, LLC

Satish Kumar Chittamuru

Scott Michael Wiltamuth

Rajiv Kumar

Alan W Carter

Ilan Gabriel Caron

Jagdish Singh

Sai Shankar

Arvind Kumar Krishnan

Namendra Kumar

Burra Gopal

Rolando Jimenez Salgado

David Koronthaly

Patrick Dengler

Sushil Kumar

Lawrence M Sanchez

Ricard Roma I Dalfó

Rakesh Gupta

Ashish Kumar Singhal

Mei-Chin Tsai

Himesh Shah

Zoltan Pekic

Harsh Vardhan Singh

Jagdeesh Shukla

Anup Sivadas

Shyam Sundar Jayshankar

Nabarun Mondal

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

Client side based data synchronization and storage is accomplished through a smart way of data off-lining coupled with a synchronization technique implemented on the client side that does not require any modifications to the server side. The customized client utilizes the server as a temporary placeholder for document synchronization. Attached documents to an item will be off-loaded from the client based on a predetermined policy. The clients make off-line copies of the items and documents. The server will maintain only the document store skeleton or metadata for such processed items. Any client which has not made an off-line copy of an item will pass a synchronization request via the server to the other clients so that at least one of its peers may upload the document onto the server. The requesting client can then retrieve the item from the server and synchronize/off-line that item on its local store.

Client side based data synchronization and storage

Recurring appointment items in a calendaring application are synchronized and recorded in a backend Line Of Business (LOB) service. Items marked in the calendaring application for time recording are used to create a recurring bound item with extended properties. A sweeper module scans on every run the mailbox for such recurring bound items. Occurrences of bound recurring appointments, which occur between the last scan and the current scan, are determined and detached from the corresponding recurring series, such that standalone bound items, are created for such occurrences that can be recognized by an LOB application. Entries for bound items are retrieved from a client data store and synchronized it with the backend LOB service through a create, update, or delete operation request.

Achieving recurring item recordings from calendaring applications over LOB systems

The system for instance customization with application independent programming of controls functions to place code behind documents in a multi-program environment in a manner that eliminates the object instance management problems of existing systems. The system consists of the process whereby the behavior of an object is changed by the user without changing its identity. In particular, the system for instance customization with application independent programming of controls combines a customizable object and a language engine object to form the customized instance of the object. Instance customization is enabled by the customized object aggregating the user defined customizations into a standard object that is supplied by Visual Basic. The Visual Basic object is given a pointer to the standard part of the document object which implements the base functionality of the document.

System for instance customization with application independent programming of controls

The system for instance customization functions to place code behind documents in a multi-program environment in a manner that eliminates the object instance management problems of existing systems. The system for instance customization consists of the process whereby the behavior of an object is changed by the user without changing its identity. In particular, the system for instance customization combines a customizable object and a language engine object to form the customized instance of the object. Instance customization is enabled by the customized object aggregating the user defined customizations into a standard object that is supplied by Visual Basic. The Visual Basic object is given a pointer to the standard part of the document object which implements the base functionality of the document.

System for instance customization

Growing community of inventors

Hyderabad Telangana, India

Satish Kumar Chittamuru