Tuesday, April 03, 2012 2:48 PM
We have used reference code to implement a tested and functional synch solution using SQL CE as the client and SQL Server as a central server. Now that we are moving into production, we have encountered an issue due to production policies that forbid the opening of SQL server ports.
Our code uses the SqlCeSyncScopeProvisioning class to provision as follows (pseudocode):
SqlCeConnection clientConnection = new SqlCeConnection("[... client connection string...]");
SqlConnection serverConnection serverConnection = new SqlConnection("[... server connection string...]");
DbSyncScopeDescription scopeDescription = SqlSyncDescriptionBuilder.GetDescriptionForScope("[...scope name...]", serverConnection);
SqlCeSyncScopeProvisioning clientProv = new SqlCeSyncScopeProvisioning(clientConnection, scopeDescription);
How can we accomplish the same thing, without requiring a direct connection to the server?
Thursday, April 05, 2012 10:24 AMModerator
you can generate a snapshot SDF and use that to initialize client...
but your issue on the connection is not limited to the provisioning but to the actual sync as well not unless you're using an n-tier setup synching via WCF.
- Marked As Answer by Crile Thursday, April 05, 2012 12:24 PM
Thursday, April 05, 2012 12:25 PMI should have updated the post. We discovered CE snapshot provisioning and it seems to be working. We were already using WCF to allow sync without a direct connection. Crile