Using ado.net

[TonyJ]

Hello!!

I have earlier used ADO.NET 1.1 when working with VS2003.and I'm quite used
to that.

We have now VS2005 so I can now use ADO.NET 2.0.

I just wonder is it great difference working with ADO.NET 2.0 compare to
ADO.NET 1.1?

Do I lose a lot of functionality and performance if I still use ADO.NET 1.1
in VS2005?

//Tony

 

[Nicholas Paldino [.NET/C# MVP]]

Tony,

I wouldn't say that you will lose performance. If anything, I think you
will gain performance. One of the things about ADO.NET which I like is just
the general model. DataTables in .NET just store data, that's it. The idea
of a current row doesn't exist. That's handled by data binding. Filtering
and sorting are also separated from data storage, in the form of DataViews.

The only bad thing is that if you are doing pessimistic concurrency,
then there is no support for that in ADO.NET. It is using a strictly
optimistic, disconnected model.

 

[Guest]

Tony,
I don't think you can use ADO.NET 1.1 with Visual Studio 2005 because it
targets the 2.0 Framework - so you will be using ADO.NET 2.0 whether you like
it or not.
You'll find ADO.NET 2.0 almost exactly like ADO.NET 1.1, with some
additional nice features.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

 

[Rad [Visual C# MVP]]

Hello!!

I have earlier used ADO.NET 1.1 when working with VS2003.and I'm quite used
to that.

We have now VS2005 so I can now use ADO.NET 2.0.

I just wonder is it great difference working with ADO.NET 2.0 compare to
ADO.NET 1.1?

Do I lose a lot of functionality and performance if I still use ADO.NET 1.1
in VS2005?

//Tony

There's not much of a difference... and when there are, they are
usually improvements in functionality and performance.

Unless there's an overwhelming reason, I'd move to ADO.NET 2

 

[Nicholas Paldino [.NET/C# MVP]]

Tony,

My apologies. Looking at the other responses, I realize that I misread
your question. For some reason, when I saw ADO.NET 1.1, I thought of the
old ADO model (the COM based one), which is what my response was based on.

Sorry for any confusion I might have contributed to.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Tony,

I wouldn't say that you will lose performance. If anything, I think
you will gain performance. One of the things about ADO.NET which I like
is just the general model. DataTables in .NET just store data, that's it.
The idea of a current row doesn't exist. That's handled by data binding.
Filtering and sorting are also separated from data storage, in the form of
DataViews.

The only bad thing is that if you are doing pessimistic concurrency,
then there is no support for that in ADO.NET. It is using a strictly
optimistic, disconnected model.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Hello!!

I have earlier used ADO.NET 1.1 when working with VS2003.and I'm quite
used
to that.

We have now VS2005 so I can now use ADO.NET 2.0.

I just wonder is it great difference working with ADO.NET 2.0 compare to
ADO.NET 1.1?

Do I lose a lot of functionality and performance if I still use ADO.NET
1.1
in VS2005?

//Tony