dotConnect vs. SqlClient

SRing · Post by **SRing** » Tue 28 Feb 2012 22:37

A number of your classes (ex. SqlCommand) are the same as those already
provided by SqlClient. So, what's the advantage of using your classes in
place of those that are built into .net? Can they be mixed and matched,
can I use a SqlClient.SqlConnection with your SqlDataTable?

Pinturiccio · Post by **Pinturiccio** » Wed 29 Feb 2012 12:17

SRing wrote:A number of your classes (ex. SqlCommand) are the same as those already
provided by SqlClient. So, what's the advantage of using your classes in
place of those that are built into .net?

These classes are not the same. They have some advantages. For example, Devart.Data.SqlServer.SqlConnection has a design-time editor. You can drag SqlConnection from Toolbox on your form and configure it with the editor. Devart.Data.SqlServer.SqlConnection works in the same way as SqlClient.SqlConnection in runtime.
The SqlDataTable class extends the Devart.Common.DbDataTable class to provide a single object that can be used to access and update data from a data source. Actually, SqlDataTable replaces SqlConnection, SqlCommand, SqlDataAdapter, and SqlCommandBuilder classes with all-in-one class. For more information, please refer to http://www.devart.com/dotconnect/sqlser ... Table.html

SRing wrote:Can they be mixed and matched,
can I use a SqlClient.SqlConnection with your SqlDataTable?

No, you can't. You have to use Devart.Data.SqlServer.SqlConnection in SqlDataTable.

For more information about dotConnect for SQL Server advantages, please refer to http://www.devart.com/dotconnect/sqlserver/