|
 |
aspx thread: ADO.NET will be change in Beta 2..!
Message #1 by "Fredrik Normen" <fredrik.normen@e...> on Fri, 5 Jan 2001 07:53:32 -0000
|
|
ADO.NET will be different in Beta 2.
The SQLDataSetCommand will be change to SqlDataAdapter, and the
FillDataSet method will be change to Fill.
The SQL managed provider will have implicit connection pooling.
The new namespace will be System.Data.SqlClient
The ADO manage provider will be change to OLEDB instead.
So ADOConnection, ADODataReader, ADOCommand, ADODataSetCommand will be:
OleDbConnection, OleDbDataReader, OleDbCommand, OleDbDataAdapter.
The new namespace will be System.Data.OleDb
There will be more changes and more API for Beta 2 but after that there
should not be so many changes.
/Fredrik Normén
---
http://www.asptoday.com - the leading site for timely,
in-depth information for ASP developers everywhere.
---
You are currently subscribed to aspx as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-aspx-$subst('Recip.MemberIDChar')@p2p.wrox.com
Message #2 by "Mike Amundsen" <mike@a...> on Fri, 5 Jan 2001 14:30:12 -0500
|
|
I'm curious...
Currently, with System.Data.ADO the following connection string is legal:
ADOConnection adoConn = new ADOConnection("DRIVER={Microsoft Access Driver
(*.mdb)}; DBQ=" +
mdbPath);
Notice the use of the DRIVER= attribute in the conneciton string.
However, with System.Data.SQL no Provider or Driver attribute is used. I
assume this is because the Data.SQL classes use OleDb exclusively.
Now, in BETA2 I'm told that the System.Data.ADO will be called
System.Data.OleDb. Does this mean that we will no longer include DRIVER or
PROVIDER attributes for connection strings in this class? Does it mean the
only legal connections will use OLEDB and we will not be able to use ODBC
anymore?
MCA
----- Original Message -----
From: "Fredrik Normen" <fredrik.normen@e...>
To: "ASP+" <aspx@p...>
Sent: Friday, January 05, 2001 2:53 AM
Subject: [aspx] ADO.NET will be change in Beta 2..!
> ADO.NET will be different in Beta 2.
>
> The SQLDataSetCommand will be change to SqlDataAdapter, and the
> FillDataSet method will be change to Fill.
> The SQL managed provider will have implicit connection pooling.
> The new namespace will be System.Data.SqlClient
>
> The ADO manage provider will be change to OLEDB instead.
> So ADOConnection, ADODataReader, ADOCommand, ADODataSetCommand will be:
> OleDbConnection, OleDbDataReader, OleDbCommand, OleDbDataAdapter.
> The new namespace will be System.Data.OleDb
>
> There will be more changes and more API for Beta 2 but after that there
> should not be so many changes.
>
> /Fredrik Normin
>
---
http://www.asptoday.com - the leading site for timely,
in-depth information for ASP developers everywhere.
---
You are currently subscribed to aspx as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-aspx-$subst('Recip.MemberIDChar')@p2p.wrox.com
Message #3 by Nathen Grass <Grass@r...> on Fri, 5 Jan 2001 15:38:17 -0500
|
|
The SQL Managed Provider doesn't use OleDB but uses Tabulardata Stream to
communicate with SQL Server. It bypasses OleDB altogether. The ADO Managed
Provider (or is it called the OleDb managed provider now?) uses OleDB to
communicate with a data store. As far as the connection strings go I assume
they will stay the same as they are now.
-----Original Message-----
From: Mike Amundsen [mailto:mike@a...]
Sent: Friday, January 05, 2001 2:30 PM
To: ASP+
Subject: [aspx] Re: ADO.NET will be change in Beta 2..!
I'm curious...
Currently, with System.Data.ADO the following connection string is legal:
ADOConnection adoConn = new ADOConnection("DRIVER={Microsoft Access Driver
(*.mdb)}; DBQ=" +
mdbPath);
Notice the use of the DRIVER= attribute in the conneciton string.
However, with System.Data.SQL no Provider or Driver attribute is used. I
assume this is because the Data.SQL classes use OleDb exclusively.
Now, in BETA2 I'm told that the System.Data.ADO will be called
System.Data.OleDb. Does this mean that we will no longer include DRIVER or
PROVIDER attributes for connection strings in this class? Does it mean the
only legal connections will use OLEDB and we will not be able to use ODBC
anymore?
MCA
----- Original Message -----
From: "Fredrik Normen" <fredrik.normen@e...>
To: "ASP+" <aspx@p...>
Sent: Friday, January 05, 2001 2:53 AM
Subject: [aspx] ADO.NET will be change in Beta 2..!
> ADO.NET will be different in Beta 2.
>
> The SQLDataSetCommand will be change to SqlDataAdapter, and the
> FillDataSet method will be change to Fill.
> The SQL managed provider will have implicit connection pooling.
> The new namespace will be System.Data.SqlClient
>
> The ADO manage provider will be change to OLEDB instead.
> So ADOConnection, ADODataReader, ADOCommand, ADODataSetCommand will be:
> OleDbConnection, OleDbDataReader, OleDbCommand, OleDbDataAdapter.
> The new namespace will be System.Data.OleDb
>
> There will be more changes and more API for Beta 2 but after that there
> should not be so many changes.
>
> /Fredrik Normin
>
---
http://www.asptoday.com - the leading site for timely,
in-depth information for ASP developers everywhere.
---
You are currently subscribed to aspx as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-aspx-$subst('Recip.MemberIDChar')@p2p.wrox.com
Message #4 by "Thomas Tomiczek" <t.tomiczek@t...> on Fri, 5 Jan 2001 21:31:49 +0100
|
|
Mike,
read the manuals, really - its some usefull information in there.
Basically:
(a) The CURRENT System.Data.SQL Namespace was NEITHER using OLEDB NOR
ODBC, but DIRECTLY going against the SQL Server WIRE LEVEL PROTOCOL. It
will be continued as System.Data.SQLClient.
(b) The current System.Data.ADO Namespace was, LIKE ADO IN THE PAST,
using OleDB. Now, even in Current VB, when using OLEDB, you CAN NOT USE
an ODBC driver, you ALWAYS go to an OLEDB Driver - and there is a
default driver that THEN tries to use an ODBC driver.
Thomas Tomiczek
THONA Consulting
-----Original Message-----
From: Mike Amundsen [mailto:mike@a...]
Sent: Freitag, 5. Januar 2001 20:30
To: ASP+
Subject: [aspx] Re: ADO.NET will be change in Beta 2..!
I'm curious...
Currently, with System.Data.ADO the following connection string is
legal:
ADOConnection adoConn =3D new ADOConnection("DRIVER=3D{Microsoft Access
Driver
(*.mdb)}; DBQ=3D" +
mdbPath);
Notice the use of the DRIVER=3D attribute in the conneciton string.
However, with System.Data.SQL no Provider or Driver attribute is used.
I
assume this is because the Data.SQL classes use OleDb exclusively.
Now, in BETA2 I'm told that the System.Data.ADO will be called
System.Data.OleDb. Does this mean that we will no longer include DRIVER
or
PROVIDER attributes for connection strings in this class? Does it mean
the
only legal connections will use OLEDB and we will not be able to use
ODBC
anymore?
MCA
---
http://www.asptoday.com - the leading site for timely,
in-depth information for ASP developers everywhere.
---
You are currently subscribed to aspx as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-aspx-$subst('Recip.MemberIDChar')@p2p.wrox.com
|
|
|
View Cart
