

Main Categories
Most popular tutorials
Latest tutorials on Geekpedia
RSS and Klip feeds
More Resources
Optimize Magazine
We have 36 Miscellaneous tutorials, you can see below:
A class that encapsulates SQL connection classes to make queries and stored procedures very easy to run in .NET. Contains methods like ExecuteStoredProcedure and ExcuteSelectStatement to return DataSets.
Put language-dependent column captions in the DataSet itself and use it in your code wherever you need it!
ADO.NET provides two basic strategies for how you work with the disconnected data model
Working with disconnected DataSets that contain autoincrement count.
How to use the event handlers for various ADO.NET connection & data objects.
An example of using an XML document to generate a typed DataSet and load it.
This article describes how to add custom validation to a data column in ADO.NET.
In this article, we will see how to use ADO.NET to serialize an object model. Once we have finished with serialization, we will look at how to bind our object model to user controls.
This article will show how to accomplish these goalsuse ADO.NET as a thin data transport layer, while still taking advantage of the data-binding capabilities of .NET user interface controls. As it turns out, its pretty easy.
A description of how how to convert a .NET DataSet to an ADODB Recordset.
In this second part of the article series, we will revisit the ADO.NET CRUD operations. Only this time, we will use an application with far better architecture. Once that is done, we will move on to data binding with objects.
An extremely flexible and easy-to-use library that retrieves data in XML format, supports simple parameterized queries, stored procedures, and transactions. It can also be used as a web service.
Sometimes it is nice to prototype up a simple database application. This code may help, by providing the automatic transactional model of COM+ in a non-COM+ environment. This example uses \"Interception\" to provide automatic transactioning support for non-COM+ classes.
Allow your DataGrid to edit pictures and a whole range of other data types.
A component providing Copy functionality to a Windows Forms DataGrid. Copied data can then be pasted in Excel or a text editor.
This article demonstrates the DataGrid , ADO.NET components, and storing data into the database and retrieving from the same.
A primer on using ADO.NET with Managed extensions for Visual C++ .NET
Mixing managed and unmanaged code and using .NET library in MFC projects
Using Data Link files with SQLClient and OracleClient.
A proposed class to simulate the ADODB.Recordset behavior in .NET.
An ADO.NET recordset class.
Sometimes it is nice to prototype up a simple database application. This code may help, by providing the automatic transactional model of COM+ in a non-COM+ environment. This example uses \"Interception\" to provide automatic transactioning support for non-COM+ classes.
How to use the event handlers for various ADO.NET connection & data objects.
WQL DataProvider for ADO.NET
Extend generated Strong Typed Datasets, add your own business-specific functionality to a real DataSet object. Binding to forms and updating to a database is all done by the .NET framework. This is built on Shawn Wildermuth\'s a.k.a. ADO Guy\'s DataSetGenerator.
A description of how how to convert a .NET DataSet to an ADODB Recordset.
A step-by-step tutorial which explains 2 ways of displaying data from an SQL Server database using ADO.NET in an ASP.NET page. Every step has been explained in detail. Online demo and source code available for download.
This article shows the reverse scenario of reading an image file from disk and saving it to a database column by utilizing the SqlCommand and SqlParameter classes. With the various command classes (for example, SqlCommand, OracleCommand, OdbcCommand, and so forth) you easily can insert or modify database records by passing a SQL statement to the command class\'s constructor (or setting a command object\'s CommandText property) and then calling one of the command object\'s \"execute\" methods, such as ExecuteReader.
It seems with every new release of Visual Studio we get a new data access method. DAO, RDO, ADO...and now ADO.NET. Well, this version of Visual Studio not only introduces ADO.NET, but also the SQL .NET Data Provider. ADO.NET and the SQL .NET Data Provider introduce many new features that we cover in other tutorials. There are quite a few samples out there demonstrating how to connect your ASP.NET application to a Microsoft SQL Server database...but lets face it, not everybody uses SQL. So how can you connect your application to an ODBC or OLEDB data store? The answer is with the ODBC and OleDb .NET Data Providers. In this tutorial we will cover all three types of connections.
ADO.net Programming article which focus on both how to write efficient code and how to represent the information which take advantage of layered design of .net framework. Articles describes how you can write code efficiently and improve performance of application and avoids errors due to poor coding style.
Currently, the DataTable has minimal support for custom validation in data columns when creating extended data columns. This article shows how to add regular expression validation capabilities to the data columns by extending the ADO.NET DataColumn. The DataColumn can be validated whenever it undergoes a change, against a validator.
This paper introduces something Microsoft calls ADO.NET. Don\'t confuse this new .NET data access interface with what we have grown to know understand as ADO - I think it\'s really very different. Yes, ADO.NET and ADOc both open connections and fetch data, however, they do so in different ways using different objects and with different limitations.
This guide focuses on the use of ADO.NET to access Microsoft SQL Server 2000 by using the SQL Server .NET data provider, one of the two providers shipped with ADO.NET. Where appropriate, this guide highlights any differences that you need to be aware of when you use the OLE DB .NET data provider to access other OLE DB - aware data sources.
Data Access for .NET consists of an architecture guide and an application block. The Data Access for .NET Architecture Guide provides guidelines for implementing an ADO.NET-based data access layer in a multi-tier .NET application. It focuses on a range of common data access tasks and scenarios and presents guidance to help you choose the most appropriate approaches and techniques.
This paper introduces something Microsoft calls ADO.NET. Don't confuse this new .NET data access interface with what we have grown to know understand as ADO - I think it's really very different. Yes, ADO.NET and ADO both open connections and fetch data, however, they do so in different ways using different objects and with different limitations.
This article summarizes the new and updated features of ADO.NET 2.0, which ships with .NET Framework 2.0.