Microsoft Sync Framework

NEW POST: Invalid Cast error - What is latest Microsoft.Synchronization version?

Tschi — Thu, 04 Sep 2008 07:58:07 GMT

is there any solution for this issue?

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 22:19:44 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample uses the Metadata store to show the basic concepts that are required when building a Sync Framework application and illustrates many of the core concepts such as synchronization providers and the synchronization orchestrator.

*Sync101 RCA with Metadata Store v1.0*
Expanding on the previous sample, this samples outlines the "remote change application" (RCA) pattern used over WCF. Please note that this sample specifically requires VS 2008 (or higher) and the x86 Sync Framework SDK as Visual Studio only comes with a 32-bit development web server.

*Sync101 with Change Units*
Expanding on the first samples, this sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Required Software*
- Visual Studio 2005 (or higher)
- Microsoft Sync Framework SDK V1.0

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 21:14:07 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample uses the Metadata store to show the basic concepts that are required when building a Sync Framework application and illustrates many of the core concepts such as synchronization providers and the synchronization orchestrator.

*Sync101 RCA with Metadata Store v1.0*
Expanding on the previous sample, this samples outlines the "remote change application" (RCA) pattern used over WCF.

*Sync101 with Change Units*
Expanding on the first samples, this sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Required Software*
- Visual Studio 2005 (or higher)
- Microsoft Sync Framework SDK V1.0

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 21:13:53 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample uses the Metadata store to show the basic concepts that are required when building a Sync Framework application and illustrates many of the core concepts such as synchronization providers and the synchronization orchestrator.

*Sync101 RCA with Metadata Store v1.0 *
Expanding on the previous sample, this samples outlines the "remote change application" (RCA) pattern used over WCF.

*Sync101 with Change Units*
Expanding on the first samples, this sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Required Software*
- Visual Studio 2005 (or higher)
- Microsoft Sync Framework SDK V1.0

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 21:12:53 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Sync101 RCA with Metadata Store v1.0*
This sample illustrates explicit transactioning (batched instead of per-update) and the "remote change application" (RCA) pattern over WCF.

*Sync101 with Change Units*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Required Software*
- Visual Studio 2005 (or higher)
- Microsoft Sync Framework SDK V1.0

UPDATED WIKI: Home

liam — Thu, 14 Aug 2008 20:19:56 GMT

Microsoft Sync Framework Samples
Introducing the Microsoft Sync Framework – a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

This resource page includes a number of samples of the Microsoft Sync Framework a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

Current Samples
- Sync101 - Getting Started with Sync V1.0
- Contact Synchronization Sample - Outlook Sync
- Sync Services for ADO.NET v2 - Download Only Sync
- Sync Services for ADO.NET v2 - Adapter Builder
- SQL Express Client Synchronization Sample
- Sync Framework Tutorial
- Producing and Consuming FeedSync Feeds using Sync

UPDATED WIKI: Home

liam — Thu, 14 Aug 2008 20:19:41 GMT

Microsoft Sync Framework Samples
Introducing the Microsoft Sync Framework – a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

This resource page includes a number of samples of the Microsoft Sync Framework a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

Current Samples
- [url:Sync101 - Getting Started with Sync V1.0|https://code.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=sync&ReleaseId=1411
- Contact Synchronization Sample - Outlook Sync
- Sync Services for ADO.NET v2 - Download Only Sync
- Sync Services for ADO.NET v2 - Adapter Builder
- SQL Express Client Synchronization Sample
- Sync Framework Tutorial
- Producing and Consuming FeedSync Feeds using Sync

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 20:19:05 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Sync101 RCA with Metadata Store v1.0*
This sample illustrates explicit transactioning (batched instead of per-update) and the "remote change application" (RCA) pattern over WCF.

*Sync101 with Change Units*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

UPDATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 20:17:48 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK and are meant to show the concepts of the Microsoft Sync Framework. Each of the samples use the the SQL MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions.

*Sync101 with Metadata Store v1.0*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Sync101 RCA with Metadata Store v1.0*
This sample illustrates explicit transactioning (batched instead of per-update) and the "remote change application" (RCA) pattern over WCF.

*Sync101 with Change Units*
This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

CREATED RELEASE: Sync 101 - Getting Started with Sync Framework v1 (Aug 14, 2008)

Thu, 14 Aug 2008 20:15:34 GMT

These C# samples are meant to show the concepts of the Microsoft Sync Framework. Included on this page are three separate samples that are based on the v 1.0 release of Sync Framework SDK.

*Sync101 with Metadata Store v1.0*
This sample is meant to show the concepts of the Microsoft Sync Framework. This sample uses the MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions. This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

*Sync101 RCA with Metadata Store v1.0*
This sample is meant to show the concepts of the Microsoft Sync Framework. This sample uses the MetadataStore database as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three data stores are use to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions. This sample also illustrates explicit transactioning (batched instead of per-update) and the "remote change application" (RCA) pattern over WCF.

*Sync101 with Change Units*
This sample is meant to show the concepts of the Microsoft Sync Framework. This sample uses the MetadataStore as store for the metadata information for each replica database. This greatly simplifies the logic required to implement data synchronization between data stores. In this sample three in memory data stores are used to show how data collaboration can be accomplished and how the Sync Framework helps to minimize P2P complexities such as data conflicts / resolution and data deletions. This sample illustrates how a data store can use change units to partition data and send only data that has changed. This sample also illustrate explicit transactioning (batched instead of per-update).

NEW POST: The type or namespace name 'SqlCeMetadataStore' could not be found

DannyT — Thu, 14 Aug 2008 15:48:28 GMT

Fixed this by simply changing SqlCeMetadataStore to SqlMetadataStore :)

NEW POST: The type or namespace name 'SqlCeMetadataStore' could not be found

DannyT — Thu, 14 Aug 2008 15:42:23 GMT

I've just downloaded the latest MSF and the getting started tutorial Sync101, i've updated the references for Microsoft.Synchronization and Microsoft.Synchronization.MetadataStorage but now it appears there is no such class as SqlCeMetadataStore. Is this a change that needs updating or have I missed something?

UPDATED WIKI: Home

liam — Tue, 12 Aug 2008 23:11:14 GMT

Microsoft Sync Framework Samples
Introducing the Microsoft Sync Framework – a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

This resource page includes a number of samples of the Microsoft Sync Framework a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices with support for any data type, any data store, any transfer protocol, and network topology.

Current Samples
- Sync101 - Getting Started with Sync V1.0 CTP2
- Contact Synchronization Sample - Outlook Sync
- Sync Services for ADO.NET v2 - Download Only Sync
- Sync Services for ADO.NET v2 - Adapter Builder
- SQL Express Client Synchronization Sample
- Sync Framework Tutorial
- Producing and Consuming FeedSync Feeds using Sync

NEW POST: Where clause looks for binary data in bigint variable

dellis — Wed, 06 Aug 2008 21:28:27 GMT

Nevermind. I should have done additional digging before posting my initial comment. I haven't used timestamp data fields much in the past. I knew that you could only have a single timestamp column in a table, but I was unfamiliar with @@DBTS which sets the value to a timestamp value. What really threw me though was the fact that the value of create_timestamp was set to @@DBTS+1. What that means in practice is that a timestamp field that looks like this (0x0000000000001771) becomes this (6002) when 1 is added. That transition is confusing. Anyway, I see that the code works, but I still need to learn some things about timestamps.

NEW POST: Where clause looks for binary data in bigint variable

dellis — Wed, 06 Aug 2008 20:46:49 GMT

In the latest code sample, in the scripts, an orders table is created and the field createtimestamp is created as a bigint. Later in the same script, a stored proc named spordersincrinserts is created with 2 values passed in - @synclastreceivedanchor binary(8) and @syncnewreceivedanchor binary(8). The values are true timestamp values. spordersincrinserts performs a select where it looks for a value in createtimestamp is searched for that lies between the two timestamp values. Since create_timestamp is a bigint and not a timestamp, how is this supposed to return valid data?

CREATED RELEASE: Sync Services for ADO.NET v2 - Download Only Sync (Jul 31, 2008)

Thu, 31 Jul 2008 18:56:54 GMT

This sample demonstrates two-tier download-only synchronization using Microsoft Sync Services for ADO.NET v2.0. The sample solution is composed of two projects: Client, which includes the UI form, data access code, and synchronization agent code for Sync Services; and SampleServerSyncProvider, which includes server synchronization provider code for Sync Services. For more information, see the code comments that are included in each file.

*Requirements*
* VS 2008 SP1
* SQL Server 2008
* Sync Services for ADO.NET v2

CREATED RELEASE: Sync Services for ADO.NET Adapter Builder (Jul 31, 2008)

Thu, 31 Jul 2008 18:54:26 GMT

This sample utility demonstrates how to create synchronization commands by using the SqlSyncAdapterBuilder in Microsoft Sync Services for ADO.NET v2. The sample solution is composed of one project that includes the UI form, data access code, and SqlSyncAdapterBuilder code.

The SqlSyncAdapterBuilder is typically used at run time to generate synchronization commands, which are in the form of SQL queries. This provides an alternative to writing these commands manually at design time. In this sample, we use the SqlSyncAdapterBuilder to output synchronization commands. You can output commands that work with SQL Server change tracking (available in SQL Server 2008) or a custom change tracking system. Running this application enables you to see how the commands are structured, and to copy those commands for use in applicatons where you will specify commands manually. For more information, see the code comments that are included in the AdapterBuilder file and Sync Services Books Online.

*Requirements*
* VS 2008 SP1
* SQL Server 2008
* Sync Services for ADO.NET v2

NEW POST: Imported projuect c:\microsoft.visualbasic.targets. not found

alexhiggins732 — Mon, 28 Jul 2008 16:38:37 GMT

that about says it. I can't load the getting started with vb demo project....

NEW POST: Invalid Cast error - What is latest Microsoft.Synchronization version?

treybe — Wed, 09 Jul 2008 15:36:05 GMT

I am getting the same error. Is there any resolve to this issue? I had the sample working fine until I updated the version of the assembly. When I updated I removed the version 1 and installed version 2. Then started getting the error.

NEW POST: Invalid Cast error - What is latest Microsoft.Synchronization version?

ClarityDon — Sun, 29 Jun 2008 22:07:54 GMT

When I attempt to run the SQLExpressProviderSample I get the following error on line 73 in SqlExpressProviderSample.SyncEngine.cs.

"Microsoft.Synchronization.Data.ClientSyncProvider"}
System.InvalidCastException: Microsoft.Synchronization.Data.ClientSyncProvider
Data: {System.Collections.ListDictionaryInternal}
HelpLink: null
InnerException: null
Message: "Microsoft.Synchronization.Data.ClientSyncProvider"
Source: "Microsoft.Synchronization.Data"
StackTrace: " at Microsoft.Synchronization.SyncAgent.setLocalProvider(SyncProvider value)\r\n at SQLExpressProviderSample.SyncEngine.Synchronize() in C:\\dload\\MS Sync Framework\\SqlExpressClientSyncProvider\\SQLExpressProviderSample\\Sample\\SyncEngine.cs:line 73\r\n at SQLExpressProviderSample.SyncForm.buttonSynchronizeClick(Object sender, EventArgs e) in C:\\dload\\MS Sync Framework\\SqlExpressClientSyncProvider\\SQLExpressProviderSample\\Sample\\SyncForm.cs:line 110"
TargetSite: {Void set_LocalProvider(Microsoft.Synchronization.SyncProvider)}

When I initially installed the CTP2 and opened this sample the Microsoft.Synchronization reference had an exclamation mark indicating an invalid reference. I removed the reference and re-added a reference to the assembly found in my GAC. I have the following version on my Vista x32 workstation: Microsoft.Synchronization, version 0.94.1142.0

I installed the following packages (in this order) when trying to set up the framework:
CTP2SyncSetup_x86.exe
CTP2SyncServicesADO_x86.msi

Is this the proper version of the Microsoft.Synchronization assembly for the sample?