Abstract: Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Abstract: Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Abstract: Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Abstract: Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Abstract: A contextual file manager is described herein. Contextual information regarding files and folders of a file system of an operating system is collected. The contextual information may be collected from a variety of different sources, such as contents of the file or folder, an application associated with the file, a service provider, or a cloud storage service. The contextual information is then exposed in a file system interface of the operating system along with representations of the files and folders. In some cases, the contextual information is exposed in response to detection of an intuitive user action to a representation of one of the files or folders via the file system interface.

Abstract: Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Abstract: A contextual file manager is described herein. Contextual information regarding files and folders of a file system of an operating system is collected. The contextual information may be collected from a variety of different sources, such as contents of the file or folder, an application associated with the file, a service provider, or a cloud storage service. The contextual information is then exposed in a file system interface of the operating system along with representations of the files and folders. In some cases, the contextual information is exposed in response to detection of an intuitive user action to a representation of one of the files or folders via the file system interface.

Abstract: The principles of the present invention extend to efficiently and reliably providing message related data. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. An electronic message can include links to folder items that represent message folders. An electronic message can also include links to contact items that represent message participants. Message applications can register for folder spaces such that each message application is aware of folders that are primarily controlled by other message applications. A link to a contact item can be selected to access current contact related data for a message participant, even when the contact related data has changed since an electronic message containing the link was received.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for efficiently storing and accessing electronic messages. Generally, electronic messages are created and transformed in accordance with an electronic message schema hierarchy. Electronic messages can be created according to a general message schema that defines a format for data fields that are common to all types of electronic messages (e.g. electronic mail, instant message, fax message). Electronic messages can also be extended according to message extension schemas that define formats for adding protocol specific and/or or application specific data fields to an electronic message. Data fields added in accordance with message extension schemas can differ between electronic messages types.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for decoupling an attachment from an electronic message that included the attachment. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. Attachments are configured to have a data field indicating if the attachment is to persist when a corresponding electronic message is deleted. When an attachment persists, a user may be able to locate and use the attachment after a corresponding electronic message has been deleted (even if the attachment has not been expressly saved). Attachments are configured to include attachment metadata indicating properties of an electronic message that included the attachment. Accordingly, a user can access information (e.g., sender, subject, date, etc) associated with an electronic message (e.g., that included the attachment) even after the electronic message has been deleted.

Abstract: The principles of the present invention extend to efficiently and reliably providing message related data. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. An electronic message can include links to folder items that represent message folders. An electronic message can also include links to contact items that represent message participants. Message applications can register for folder spaces such that each message application is aware of folders that are primarily controlled by other message applications. A link to a contact item can be selected to access current contact related data for a message participant, even when the contact related data has changed since an electronic message containing the link was received.

Abstract: The principles of the present invention extend to efficiently and reliably providing message related data. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. An electronic message can include links to folder items that represent message folders. An electronic message can also include links to contact items that represent message participants. Message applications can register for folder spaces such that each message application is aware of folders that are primarily controlled by other message applications. A link to a contact item can be selected to access current contact related data for a message participant, even when the contact related data has changed since an electronic message containing the link was received.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for presenting different types of electronic messages at a common interface. Electronic message items are stored in an item database along with other types of items, such as, for example, contact items, folder items, document items, etc. Electronic message items have some common defined data fields and possibly other differently defined data fields that represent protocol and/or application specific properties. Computer systems can query the item database for message related data (e.g., from commonly defined data fields) and display links to message related data at a common messaging interface. Links to different types of electronic messages (as represented by protocol and/or application specific properties) may be displayed simultaneously at the common messaging interface.