ActiveSync is the latest software release for synchronizing Windows Mobile-based devices with Windows XP. Microsoft ActiveSync provides a great synchronization experience with XP-based PCs and Microsoft Outlook right out of the box. ActiveSync acts as the gateway between your PC and Windows Mobile-based device, enabling the transfer of Outlook information, Office documents, pictures, music, videos and applications from your desktop to your device. In addition to synchronizing with a desktop PC, ActiveSync can synchronize directly with Microsoft Exchange Server so that you can keep your e-mail, calendar data, notes and contact information updated wirelessly when you're away from your PC.
Introduction to Microsoft Sync Framework Microsoft Corporation October 2009 Introduction Microsoft Sync Framework is a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices. Developers can build synchronization ecosystems that integrate any application, any data from any store using any protocol over any network. Sync Framework features technologies and tools that enable roaming, sharing, and taking data offline. A key aspect of Sync Framework is the ability to create custom providers. Providers enable any data sources to participate in the Sync Framework synchronization process, allowing peer-to-peer synchronization to occur. Windos Media Player 10. A number of providers are included by Sync Framework that support many common data sources. Although they are not required, to minimize development it is recommended that developers use these providers wherever possible.
Announcing Microsoft Support and Recovery Assistant for Office 365. Feb 14, 2007 ActiveSync is the latest software release for synchronizing Windows Mobile-based devices with Windows XP. Microsoft ActiveSync provides a great synchronization experience with XP-based PCs and Microsoft Outlook right out of the box. ActiveSync acts as the gateway between your PC and Windows Mobile. ActiveSync for Windows Mobile, free and safe download. ActiveSync latest version: Microsoft's classic synchronisation utility. Announcing Microsoft Support and Recovery Assistant for Office 365.
The following are the providers included: • Database synchronization providers: Synchronization for ADO.NET-enabled data sources • File synchronization provider: Synchronization for files and folders • Web synchronization components: Synchronization for FeedSync feeds such as RSS and ATOM feeds Developers can ultimately use any of the out-of-the-box providers or can create custom providers to exchange information between devices and applications. The goal of this document is to help you understand how Microsoft Sync Framework enables synchronization. In this document we will outline some key concepts that will form the basis for how to create a provider. Participants Before discussing the specific components of a provider, we first need to understand the different types of participants that can be supported. A participant is the location where information from the data source is retrieved.
A participant could be anything from a web service, to a laptop, to a USB thumb drive. Participant Types Based on the capabilities of the device, the way that a provider integrates synchronization will vary.
At the very least, we will assume that the device is capable of programmatically returning information when requested. Ultimately, what needs to be determined is if the device can: • Enable information to be stored and manipulated either on the existing device or within the current data store, and; • Allow applications (in our case a synchronization provider) to be executed directly from the device It is important to distinguish the types of participants that will be part of the synchronization ecosystem because it tells us if they will be able to store the state information required by the provider and it also tells us if we are able to execute the provider directly from the device. Ultimately, the participant model is meant to be generic. As such, a full participant could be configured to be either a partial or simple participant. Full Participants Full participants are devices that allow developers to create applications and new data stores directly on the device.
A laptop or a Smartphone are examples of full participants because new applications can be executed directly from the device and you can also create new data stores to persist information if required. Partial Participants Partial participants are devices that have the ability to store data either in the existing data store or another data store on the device. These devices, however, do not have the ability to launch executables directly from the device. Some examples of these participants are thumb drives or SD Cards. These devices act like a hard drive where information can be created, updated or deleted.
However, they do not typically give an interface that allows applications to be executed on them directly. Simple Participants Simple participants are devices that are only capable of providing information when requested. These devices cannot store or manipulate new data and are unable to support the creation of new applications. RSS Feeds and web services provided by an external organization such as Amazon or EBay are both examples of simple participants. These organizations may give you the ability to execute web services and get results back, however, they do not give you the ability to create your own data stores and they also do not give you the ability to create your own applications to be executed within their web servers. Bringing it All Together Ultimately the goal of Microsoft Sync Framework is to allow any data source to be integrated regardless of the participant type.
For this reason, partial participants can synchronize information with full participants and full participants can synchronize information with simple participants. At the very least there needs to be one full participant that has the ability to store information and launch the synchronization process. Microsoft Synchronization Framework Core Components Before implementing synchronization using Sync Framework, we need to first understand the key components of a provider. The following diagram shows how a provider built using Sync Framework communicates with a data source and retrieves state information from a metadata store.
These providers in turn communicate with other providers through a synchronization session. Data Source The data source is the location where all information which needs to be synchronized is stored. A data source could be a relational database, a file, a Web Service or even a custom data source included within a line of business application. As long as you can programmatically access the data, it can participate in synchronization.
Metadata A fundamental component of a provider is the ability to store information about the data store and the objects within that data store with respect to state and change information. Metadata can be stored in a file, within a database or within the data source being synchronized.