| .NET Anatomy - ADO.NET in Beta2 : Part 1 |
| DotNetJunkies |
| This article reviews the ADO.NET object model found in Microsoft’s .NET Framework Beta2. The information presented here will be useful both to programmers who worked with Beta1 and also, to those just starting with the framework. |
|
| .NET Anatomy - ADO.NET in Beta2 : Part 2 |
| DotNetJunkies |
| In my last article I reviewed the ADO.NET object model as it is presented in the .NET framework Beta2. To put this information to practical use, this article will provide a walkthrough of how to use Microsoft's newest set of developer tools, found in Visual Studio.NET to create a working Web Application that accesses an SQL database. |
|
| .NET Anatomy - Data Concurrency in ADO.NET, Part I |
| DotNetJunkies |
| This article is the beginning of a multi-part article that discusses data concurrency in ADO.NET and reviews how the ADO.NET model supports multi-user scenarios where data may be updated at the server while an ADO.NET client is using that data. |
|
| .NET Connector for Microsoft Outlook |
| The Code Project |
| Export Microsoft Outlook data using XML DataSets and the Outlook COM Object Library. |
|
| A C# Web Spider written as a Web Service |
| C#Today |
| A Web Spider is a program that is used to navigate sites, follow links and collect various information. It is sometimes called a Web Robot. In this article. ST Tan & Aldy Karna discuss the subject, and show how a Web Spider can be written in C#. |
|
| Accessing Oracle 9i Stored Procedures Using ADO.NET |
| MSDN |
| Use the .NET Oracle Provider in the Microsoft .NET Framework version 1.1 to access Oracle stored procedures and functions. |
|
| Add Professional Quality Reports to Your Application with Visual Studio .NET |
| MSDN |
| Crystal Reports for Visual Studio .NET provides a comprehensive reporting solution for .NET developers that is thoroughly integrated with both the Visual Studio .NET IDE and the .NET Framework. Crystal Reports supports ADO.NET, XML Web Services, and ASP.NET server controls and caching. It also integrates seamlessly with the Visual Studio .NET Server Explorer, toolbox, and design environment. It has a rich programming model and flexible options for customizing and deploying reports. These major features and others covered here take the drudge work out of data representation in your own applications. |
|
| ADO .NET for the ADO Programmer |
| MSDN |
| ADO .NET is the latest in a long line of database access technologies that began with the Open Database Connectivity (ODBC) application programming interface (API) several years ago. Along the way, a number of interesting things happened. For example, COM landed at the database territory and started a colonization process that culminated with OLE DB. Next, ActiveX® Data Objects (ADO)—roughly an automation version of OLE DB—has been elected to govern the Visual Basic® and ASP community of Windows®-based database developers. |
|
| ADO.NET 2.0 Feature Matrix |
| MSDN |
| ADO.NET 2.0 includes a new base-class provider model, features for all providers, and changes to System.Data.SqlClient. Get an overview of these new features, examples of their use, and a chart of which features are provider-neutral and SqlClient-specific. |
|
| Advanced Data Access with ADO.NET and Oracle |
| MSDN |
| Learn how to use ADO.NET 1.1 to retrieve data from complex Oracle data types. |
|
| An ADO.NET multi-tier solution |
| The Code Project |
| A view of how ado.net can be used in a multi-tier environment. |
|
| An introduction to a post-relational database for .NET : Matisse - Part 4 |
| The Code Project |
| ADO.NET programming with a post-relational database |
|
| Article 2 - Dynamic creation of database |
| The Code Project |
| Display data using Dataset and Data Grid control after the database is created |
|
| BETA-PRB: CommandBuilder Changes Modified Commands Back to Original (Q310366) |
| Microsoft Support |
| The CommandBuilder object may rebuild a command that you try to modify during the next call to the DataAdapter.Update method, and your changes to the command may be lost. |
|
| BETA-PRB: Error "Unhandled Exception of Type System.NullReferenceException Occurred in CommandBuilder" (Q310367) |
| Microsoft Support |
| If you use the CommandBuilder object to explicitly get commands for the DataAdapter object as follows you can receive the following error message: "An unhandled exception of type 'System.NullReferenceException' occurred in commandbuilder (projectname).exe. Additional information: Value null was found where an instance of an object was required."
|
|
| Binding a DataGrid to an ADO Recordset |
| DotNetJunkies |
| Sooner or later you're going to need to bind a control to an ADO Recordset. The most likely reason is that you need to leverage a control written in COM that returns a recordset. As you will see, this is actually a very easy thing to do. |
|
| BUG: The DataAdapter Wizard generates an InsertCommand property that includes timestamp columns |
| http://www.kbalertz.com/ |
| (815543) - When you have a timestamp column in the query of the DataAdapter Wizard, the timestamp column is included in the InsertCommand property of the DataAdapter object. The DataAdapter Wizard uses OLE DB or Microsoft SQL Client .NET Data Providers. Although... |
|
| BUG: The DataAdapter Wizard generates an InsertCommand property that includes timestamp columns |
| Microsoft Support |
|
(815543) - When you have a timestamp column in the query of the DataAdapter Wizard, the timestamp column is included in the InsertCommand property of the DataAdapter object. The DataAdapter Wizard uses OLE DB or Microsoft SQL Client .NET Data Providers. Although...
|
|
| BUG: The DataAdapter Wizard generates an InsertCommand property that includes timestamp columns |
| Microsoft Support |
| (815543) - When you have a timestamp column in the query of the DataAdapter Wizard, the timestamp column is included in the InsertCommand property of the DataAdapter object. The DataAdapter Wizard uses OLE DB or Microsoft SQL Client .NET Data Providers. Although... |
|
| Build a Universal DAL Component |
| DotNetJunkies |
| Think about the possibilities of a component in the data access layer (DAL) of your application that didn't care what .NET Data Provider you were using. It could work just as easily with the SQL Server Data Provider or the OleDb Data Provider, or any other potential .NET Data Providers that could surface in the future. A DAL component that you could use against an Access 2000 database in development, and against a SQL Server database in production. In this tutorial, Doug shows how to build a universal data |
|
| Building a Custom Data Provider for Use with the .NET Data Access Framework |
| MSDN |
| The System.Data.dll assembly in the .NET Framework contains namespaces whose base classes can be used to create custom data providers. These namespaces also define a number of data access interfaces and base classes that let developers create data providers that will interoperate with other custom providers. Using the ADO.NET classes Connection, Command, DataReader, and DataAdapter, writing a provider is easier than writing one for OLE DB. This article explains these classes and their implementation, and how they can be used to write a variety of different kinds of data providers. |
|
| Building a Generic Database Tool Using .NET and Three Tier Architecture |
| DotNetJunkies |
| In this article, Sun shows how easy it is to develop a n–tiered Web application to create a generic database tool using ASP.NET and the .NET Framework. The system is quite simple and is able to handle the management of any simple table in any database. It provides an excellent starting point for providing a generic database tool. |
|
| Building a Tiered Web App Using the DataSet and the ASP DataGrid |
| MSDN |
| This month, I'll walk through the development of a three-tiered Web application that retrieves data, allows the user to make changes, and sends the data back to the database using the DataSet object as the transport mechanism. |
|
| Building a Universal DAL Component |
| DotNetJunkies |
| Think about the possibilities of a component in the data access layer (DAL) of your application that didn't care what .NET Data Provider you were using. It could work just as easily with the SQL Server Data Provider or the OleDb Data Provider, or any other potential .NET Data Providers that could surface in the future. A DAL component that you could use against an Access 2000 database in development, and against a SQL Server database in production. |
|
| Building an N-Tier Application in .NET |
| MSDN |
| After reviewing the types of n-tier applications, you'll learn how to create a typed dataset that can return data from a Web service and consume a Web service from a Windows application. |
|
