Please allow dll's to be included directly in .Net projects rather than an MSI redistributable. This is a major pain. It will take many times longer for me to fight with Installshield than to integrate the sync framework in my project - arrggghhh!

simple as title

Add a sample that synchs outlook address book with hotmail. Include the flexible data field mapping, how to handle concurrent changes on both sides...

Rows cannot be deleted without the deletes being synced to the server. There is a workaround for this, but an easier method should be provided.

Currently Scopes can not be changed once created.
Changing the filter on a scope should sync any additional rows automatically.

A two way synch between Outlook and Sharepoint including Custom Fields and Public folders would enhance both products.

Currently, we only support the ability to sync a device to a central server in a hub-spoke topology. This work would be to add support for any topology shape such as synchronization between two clients.

Currently the sync framework does not have any admin interface, to monitor the sync activity. This feature would be usefull for monitoring the sync activity.

The SqlSyncProvider requires provisioning the database with added metadata (triggers, columns) instead of using the native SQL Server Change Tracking. The client/server DbSyncProvider supports native change tracking but does not support other features such as batching.

Full suppot of Azure Tables, including tables that contain entities that have different schema

Wizard steps on right col of screen. Explaination of step and choices on right. For instance create solution; add project; add roles; add database service; choose template; etc.

The P&P group has the right idea. Keep things simple and easy to use. I haven't seen a good walkthrough of what is the minimum necessary for a bare-bones sync between 2 SQL Servers. Look at the walkthroughs for Prism created by the P&P guys for great documentation/walkthroughs.

Managed, portable, open and fixable. If you need unmanaged code for legacy reasons, keep it parallel. This way, as Silverlight grows more and more powerful, we will have the chance of running the framework on various platforms. Potentially even on Linux phones, using Moonlight. With managed code, we wouldn't.

Online and Offline syncing. File system and Isolated storage support. Make it extensible and provide source code with public review. Just like ASP.NET MVC project.

filtered by value on the master and in the detail table, only on the items that are related to the filtered master items