Mahesh Chand

Data Binding and Windows Forms Data-Bound Controls

When it comes to developing interactive database applications, it’s difficult to resist using data-bound controls. Data-bound controls are easy to use, and they also provide many handy, built-in features. You used DataGrid, ListBox, and other data-bound controls in the previous chapters. In this chapter, we discuss the basics of data binding, how to use data-bound controls, and how to develop interactive database applications using these controls with a minimal amount of time and effort.

Integrating XML with ADO.NET

The programming world is moving more and more toward the Web, and Extensible Markup Language (XML) is an essential part of Web-based programming. This chapter assumes you have an understanding of basic XML syntaxes and documents.

COM Interoperability and ADO.NET

The Component Object Model (COM) has been around for many years and is used by many Windows applications. Eventually the .NET platform will replace COM, but until then you may need to develop COM components from .NET and access them from unmanaged code, or you may want to use COM components in .NET applications. COM interoperability (also referred to as COM Interop) enables you to use existing COM components in .NET applications or use.NET components in unmanaged code.

Object-Relational Mapping in .NET

Relational databases treat data in terms of rows and columns, and objects treat things in terms of arrays and properties. Object-relational mapping (OR mapping) bridges these two worlds so your code can look like object code and still store itself in a relational database.

Stored Procedures and Views

Relational databases such as SQL Server and Oracle rely on stored procedures to do repetitive tasks, so a programmer’s main jobs when creating database applications are creating, debugging, and testing stored procedures (often called stored procs). Another database object it behooves programmers to learn is the view—or virtual table. In this chapter, you’ll learn how to take advantage of Visual Studio.NET (VS.NET) tools to work with both stored procedures and views.

Mapped Objects: Performance Considerations and Data Binding

In the last chapter you learned the basics of turning the data in your database into objects. Although basic Object-Relational (OR) mapping is simple, a number of issues become apparent when it comes time to actually put it to work.

Oracle, SQLXML, and Other .NET Data Providers

In previous chapters, we discussed the Sql, OleDb, and ODBC data providers and how to use them work with various databases including SQL Server, Access, Excel, and MySQL. As mentioned, ADO.NET is flexible enough so anyone can develop their data provider and add it to the library as an add-on.

Constraints and Data Relations

In chapter 3, you encountered constraints and data relations. In this chapter, we discuss constraints and data relations in more detail. First, we start this chapter with a discussion of constraints and how ADO.NET constraint objects maintain data integrity. Second, we discuss data relations. An object that encapsulates a data relationship may be a new concept for many programmers.

ADO.NET in Disconnected Environments

In Chapter 1 and Chapter 2, you learned about ADO.NET, and you learned how to use ADO.NET components with Visual Studio (VS) .NET. You also learned how to write code that binds ADO.NET components to data-bound controls and how to use VS. NET’s Integrated Development Environment (IDE) wizards to write full-fledged database applications.

SQL Server and ADO.NET: Notes on Performance

Ever since the early days of relational databases, optimizing database performance has always been as much an art as a science. Even today, you’ll often hear of new “secrets” through professional relationships that take on the air of furtive back-alley exchanges more reminiscent of a Le Carre novel than a sober discussion between colleagues. This chapter discusses some SQL Server and ADO.NET performance issues. It also discusses some best practices to make sure you get the most out of your code.