.NET news » Search results

Basic CRUD methods with some other interesting features

ADO.NET in the next release of Visual Studio code-named "Orcas" features the new Entity Framework. It allows developers to focus on data through an object model instead of through a logical/relational data model. The Entity Framework helps abstract the logical data schema into a conceptual model and allows for multiple ways to interact with the conceptual model through Object Services and a new data provider called EntityClient. This month’s column discusses what the Entity Framework is, how it fits into an application, and how it can be designed and programmed against.

Connection pooling can increase the performance of any application by using active connections of the pool for consecutive requests, rather than creating a new connection each time. And at the same time, the developer who is the best judge of his/her application, can configure the connection pooling.

Build occasionally connected applications using Microsoft Synchronization Services for ADO.NET

The Windows Forms binding controls are vastly improved descendents of the data binding controls of the past. They get you going quickly and handle the redundant tasks associated with setting up forms, and you can customize and extend their behavior significantly. Data can travel in a variety of containers, including DataSets and custom class entities, and the Windows Forms binding tools allow you to bind to all of these types of objects. If you don't want to use a DataSet, you can create custom entities to be used as the data store for your application, and you can use List<T> and other collection types to store a set of your custom entities. These types of custom entities can easily be bound using the BindingSource and the BindingNavigator. In this column I'll demonstrate how to bind a custom list of business entities using the binding tools present in the Microsoft .NET Framework 2.0, and I'll do so by writing a fully functional data-driven Windows Forms application.

The Entity Data Model and ADO.NET vNext let you deal with tabular data as objects, eliminating much of the effort endemic to older data-retrieval and modification code.

The most popular instrument to access database data for .NET applications is ADO.NET. This set of components contains three main classes those are used to manipulate and store data: DataReader, DataSet and DataAdapter. DataReader is only able to read data and can't work as data source for data-aware components like DataGridView; DataSet provides all interfaces to be a data source but disconnected model considers some restrictions that can become important for some kind of applications, especially for desktop programs that work under multiuser concurrent environment and change database data actively. Below we consider main restrictions and popular ways to solve them; non standard solutions are considered also.

This article explains how to migrate data between different SQL Server environments.

ADO.NET vNext is a leap forward in database programming, using mapping files to isolate your applications from relational database schema changes, and letting you choose whether to deal with data directly as objects or as tabular data.

This article explains how to migrate data between different environments