.NET news » Search results

Writing database-access code is a repetitious and time-consuming task, but now that it's available as a reusable Enterprise Data Access Application Block, you'll never have to write such code again.

Modern applications require more sophisticated data access features than a simple connection to SQL Server. Data needs to be available in distributed scenarios as well as offline scenarios. This article provides an architectural overview and implementation examples that support these scenarios.

Access data in any SQL server compact edition datatable using only one line of code in C#

Do more with less code is the slogan of Visual Studio 2005.When it comes to reducing the amount of written code, wizards are definitely a viable option. Visual Studio 2005 has a lot of wizardry in it, especially to generate data access code. Any code that gets silently injected in your project follows a strict logic and a well-known design pattern. A full understanding how Visual Studio 2005 does it puts you on the right track to modify and extend the code to build your made-to-measure data access layer. This article dissects the code behind table adapters and binding source components to unveil patterns and best practices.

An application that creates a C# class to read/write data to/from an Access, SQLite, or XML database.

NCache is a high performance in-memory object caching solution for mission critical .NET applications with real-time data access needs. NCache not only lets you cache read-only data but also complex transactional data with relationships. As a result, your application can cache most of its data and dramatically improve performance.

This short introduction to.NET shows Access and SQL Server developers how to use a development tool to create connections to data and a user interface to manipulate that data.

Data integration is the cornerstone of many apps these days, which means you’ll need to add database expert to the many hats you wear. Or maybe not. We’ll show you some handy tools and resources for maximizing data access while minimizing muss and fuss.

All applications are dependent on data in some form and most developers find themselves writing reams of data access code. Microsoft has been building databinding frameworks for years. Each one promises to solve our databinding woes forever. We're still waiting for the perfect one. In the previous article you were exposed to programmatically controlling data binding mechanisms of WPF. Along with a programmatic interface, WPF also provides a declarative databining interface. This second article will introduce you to using the declarative data binding mechanisms contained in WPF.

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.