Every time I do this I have to figure it out again. (Sometimes I empathize with HAL, when he is being dismantled at the end of 2001: "My mind is going, Dave. I can feel it.") I'm blogging this as much for myself as for anyone else it might help. Here is the magic spell you need: Create a Class Library project in your solution in the supported language of your choice. I like C#, but Visual Basic .NET also works. Every time I do this I have to figure it out again. (Sometimes I empathize with HAL, when he is being dismantled at the end of 2001: “My mind is going, Dave. I can feel it.”) I’m blogging this as much for myself as for anyone else it might help.Here is the magic spell you need: Create a Class Library project in your solution in the supported language of your choice. I like C#, but Visual Basic .NET also works. I usually end the project name with DAL so that I can remember what it is. Delete the Class1.cs (or .vb) source file that is created automatically. Right-click on the project and add a new DataSet item. The design surface for an XSD file will open. Open a data connection to the database you’re wrapping. Select each table you want to use and drag it to the design surface. Build the data access layer project. Add a reference to the data access layer project to your UI project. It doesn’t really matter whether the UI project is a Windows Forms application, an ASP.NET application, a console application, or a Windows Presentation Foundation application. Add a using (or Imports) statement for the table adapters of the data access layer to your UI project. IntelliSense will help out if you added the reference properly.Now you can instantiate the table adapters in your code and call the appropriate pre-generated methods for whatever CRUD operations you need. If you need other operations, you can go back to the DAL and add them: right click at the bottom of the table in the DataSet diagram and add a query. Software Development