I am looking to build an orcas vsto outlook addin for an OBA app where I am going to use winform controls to make the addins. Many of the fields are not going to be intrinsic to the outlook store namespace (e.g. contact names etc) although many of the screens will be based on them.

The users are not going to be online all the time so hence the need for synchronization. I am understanding that I can use either of these two technologies here - which is easier, more stable, and more appropriate for this situation?

IE: use the built in outlook store object and just add whatever custom fields so that it handles the synchronization with a web service and in turn with a remote sql server

or else

use Synchronization Services for ADO.NET and have a local sql server compact ed. communicate with a remote sql server... (does this require a web svc as a go-between?)

Thanks in advance,

Tom