Welcome to MSDN Blogs Sign in | Join | Help

March 2007 - Posts

Creating your SQL Server Compact Edition database and schema in code

In most cases you'll want to create your database and it's schema as part of your applications first deployment. Depending on the scenario, you may create it on the client, or create it on the server, do the initial sync, then stream the file down to

Going N Tier w/WCF, Synchronizing data using Sync Services for ADO.NET and SQL Server Compact Edition

In part 1 , I used the Visual Studio Orcas Sync Designer to configure and synchronize 3 lookup tables to be cached locally in SQL Server Compact Edition using the Sync Services for ADO.NET CTP. In part 2 of this screen cast, I take the cached lookup tables

First look at the Visual Studio Orcas Sync Designer

Here's part 1 of the new Sync Designer. In this screen cast I walk through how to cache lookup tables locally. In this screencast I use the 2 tier sync, starting simple. In the next screencast I'll show how to take the same designer, and split it across

Additional Q&A on the Visual Studio Orcas Sync Designer

Q: Why does the Orcas Feb CTP Typed DataSet designer not work on Vista? A: Visual Studio Orcas is not yet fully compatible with Vista. In the Feb CTP there are several issues with something we call "red bits". These are changes to the runtime that shipped

Q&A on OCS & Sync Services for ADO.NET

Not surprisingly we've been get a lot of great questions about specific features and scenarios for our new Sync Services for ADO.NET (OCS). Rafik has been fielding most of these on the Sync Services forums . Since the Q&A for SQLce seemed popular,
 
Page view tracker