Geek Answers Handbook

Why switch from ADO to ADO.NET?

I have friends who are developers of VB6 "old school" databases, and I told them about .NET and its features, in particular, about ADO.NET.

In our conversation, they identified the following reasons why they prefer to stick to ADO rather than switch to ADO.NET:

  • The data set is disabled (what if the power is not working?)
  • The same amount of code still needs to be written
  • New options for Dataset , BindingSource and TableAdapter seem confusing
  • the same code is written programmatically to the database, all that changes is how this command is laid out.

I am looking for answers or reasons why ADO.NET is “better” than ADO regarding data access when it comes to Windows Forms applications. What does ADO.NET ensure that ADO does not? What does he do better than ADO?

NB: I would like to use examples that are not related to LINQ.

+4
source share
8 answers

On the one hand, if it does not break, do not correct it. But on the other - VB6? Indeed? It looks like ADO vs ADO.NET is a little potato ...

I think the problem is rather with VB and VB.NET, and then the entire code base, skill set, other non-technical considerations come into play here.

+10
source

ADO is an unsupported COM based technology. VB 6.0 is an unsupported technology since the end of the year as of March 2008. DAO, RDO, ADO - these are all technologies that surpass their scope for almost a decade.

ADO.NET is a modern set of tools for accessing data. In particular, LINQ to SQL and Entity Framework take data access to new heights.

+6
source

There is nothing wrong with using ADO in older VB6 applications. And if these applications work correctly, there is no reason to change them.

I don’t think anyone .Net programming will be too tempting to try using ADO, because it feels so hacky when you try. Just let them be.

+5
source

The simple answer: do not convince them ...

Have them take a look at LINQ to SQL (or better still LINQ to Entities)

+2
source

One of the biggest problems that allowed people to switch to ADO.NET at my day job is the fact that ADO (VB6 flavor) is all COM, you get better performance with ADO.NET.

+2
source

I heard rumors that VB6 runtime will not be sent after Windows 7 ...

0
source

I assume that if the recordset is still connected and the power is turned off on the server, will the user be immediately prompted in their application before they continue to enter data that will not be saved?

How about garbage collection memory?

Distributing updates is easier in .net.

I think if you have a lot of code in VB 6 for winform applications, why change? Perhaps if you start a new project using VB.NET, you can show some other advantages, such as including multiple tables in a table adapter (I cannot say that I took advantage of this).

0
source

I prefer ADO.NET on my own, but only for balance there is one advantage of classic ADO over ADO.NET: it is probably more useful.

Our customers have difficulty using [ADO.NET] because of its extensive initialization. Even in the simplest scenarios, users expected an understanding of the complex interactions and dependencies between several types ... Note that many of these problems were resolved in .NET. framework 2.0.

Written by the architects of the .NET framework, in . .NET Framework Design Guidelines 2nd Edition Page.

0
source

More articles:


All Articles