locked
VS 2010 Data Synchronization wizard and SyncFramework 2.1 RRS feed

  • Question

  • VS 2010 Data Synchronization wizard still uses SyncFramework 1.0 (SP1 ?). What are the minimum steps to upgrade wizard generated projects to SF 2.1? Is it enough to replace assembly references to SF 1.0 assemblies with references to SF 2.1 assemblies on both client and server projects or something else is necessary?

     

    Thank you!

    Konstantin


    Thank you! Konstantin
    Sunday, August 29, 2010 5:57 PM

Answers

  • it's the SqlSyncProvider/SqlCeSyncProvider that was updated in v2.1 and not the SqlCeClientSyncProvider/DbServerSyncProvider  used by the Local Database Wizard.

    if youre project in V1 was generated using the Local Database Cache Wizard, there is no upgrade path as they are completely different providers.

    The providers used by the wizard generated code uses anchors/sync groups while the providers that were updated in v2.1 uses knowledge/scopes and the SqlSyncProvider/SqlCeSyncProvider has not designer/wizard support.

    The SQL Compact 3.5 SP2 mentioned in the release notes is for the SqlCeSyncProvider which is again different from what the Local Database Designer uses which is the SqlCeClientSyncProvider.

    Note that 1.0 SP1 supports SQL Compact 3.5 SP2 as well.

    Tuesday, August 31, 2010 8:54 AM

All replies

  • the updates on Sync Fx 2.1 is primarily on the SqlSyncProvider/SqlCeSyncProvider.

    The Local Database Cache wizard uses the SqlCeClientSyncProvider/DbServerSyncProvider so i dont think there's any gain.

    • Proposed as answer by JuneT Tuesday, August 31, 2010 8:23 AM
    • Unproposed as answer by Konstantin Erman Tuesday, August 31, 2010 8:39 AM
    Monday, August 30, 2010 1:00 AM
  • The Sync Framework 2.1 supports SQL Server Compact 3.5 SP2. Lack of that support was holding many people from moving from 1.0 SP1 (which also supports it) to 2.0 (which does not). And I'm talking about plain Local Database Cache wizard generated projects. So there must be some gain. Another question is how exactly to upgrade 1.0 SP1 to 2.1?
    Thank you! Konstantin
    Tuesday, August 31, 2010 8:44 AM
  • it's the SqlSyncProvider/SqlCeSyncProvider that was updated in v2.1 and not the SqlCeClientSyncProvider/DbServerSyncProvider  used by the Local Database Wizard.

    if youre project in V1 was generated using the Local Database Cache Wizard, there is no upgrade path as they are completely different providers.

    The providers used by the wizard generated code uses anchors/sync groups while the providers that were updated in v2.1 uses knowledge/scopes and the SqlSyncProvider/SqlCeSyncProvider has not designer/wizard support.

    The SQL Compact 3.5 SP2 mentioned in the release notes is for the SqlCeSyncProvider which is again different from what the Local Database Designer uses which is the SqlCeClientSyncProvider.

    Note that 1.0 SP1 supports SQL Compact 3.5 SP2 as well.

    Tuesday, August 31, 2010 8:54 AM