
You can add tasks and comments to your solution. We can view the comments from the View menu --> Task List (Ctrl + W, T) which helps us to keep track of the TODO changes we left behind.
A place to explore .net concepts.

I am going to furnish you a set of steps to follow in order to configure the SQL Server 2005 in VS for ADO. Net synchronization.
If you would have read my previous blog on What is Synchronization and How they work, it will be a piece of cake for you to follow these steps.
I am going a head to describe the steps thinking that you have basic knowledge on ado.net synchronization.
a) You can select the server connection, if you have any of those in the dropdown or click the New button to create a new Sql server 2005 connection
b) Same way you can select the client connection or click the New button to create a New SQL Compact Edition ie, only Compact edition of sql server can be used as client and not SQL express
c) Click the Add button below the Cached Tables to add the table which you want to be synchronized with the Server
d) Click the “Show Code Example” link in the right most bottom of the screen and copy the code to the clipboard( a button will be there to do the operation). I will tell you were to use the this code.
e) Click OK, so that at the first time the data will be downloaded from the server to the client database.
f) It will also try to create a dataset, just click cancel.
g) For synchronization the schema of the table in the server and client will be modified and the script for this will be place in the current solution in a folder called “SQL Scripts” and “SQL Undo scripts”. This scripts does nothing but add two columns to your table for keeping track of the changes happened in offline and to sync with the Server tables. Column name “CreationDate” and “LastEditDate”
Ex. this.DataElement.SyncDirection = Microsoft.Synchronization.Data.SyncDirection.Bidirectional;
I hope you got a glimpse on how to work on ado.net sync. I will explain in my next article on how to do the same with SQL Server 2008
Sync Services for ADO.NET is a part of the Microsoft Sync Framework (MSF). MSF is a comprehensive synchronization platform that enables developers to add synchronization capabilities to applications, services and devices. MSF solves the fundamental problem of how to synchronize any type of data in any store using any protocol over any topology. Fundamental to MSF is the ability to support offline and collaboration of data between any types of endpoints (e.g. device to desktop, device to server, etc.).
Sync Services for ADO.NET enables synchronization between ADO.NET enabled databases. Since Sync Services for ADO.NET is part of the MSF, any database that uses Sync Services for ADO.NET can then also exchange information with other data sources that are supported by MSF, such as web services, file systems or custom data stores.
The primary focus of this document will be on synchronizing information between database systems and how Sync Services for ADO.NET helps developers avoid many of the common issues associated with OCAs.
ADO.net with VS2005 or VS2008 synchronization can be done with both the SQL server 2005 and 2008. MSDN link on various synchronization framework is here
For more information reach me by mail
One Early morning a mother went to her sleeping son and woke him up.
MOM : "Wake up, son. It's time to go to school."
SON : "But why, Mama? I don't want to go to school."
MOM : "Give me two reasons why you don't want to go to school."
SON : "One, all the children hate me. Two, all the teachers hate me."
MOM : "Oh! that's not a reason. Come on, you have to go to school."
SON : "Give me two good reasons WHY I *should* go to school?"
MOM :
One, you are FIFTY-TWO years old and should understand your responsibilities.
Two, you are the PRINCIPAL of the school.