为什么要从ADO切换到ADO.NET？-WhyswitchfromADOtoADO.NET?

On the one hand, if it ain't broke, don't fix it. But on the other - VB6? Really? Sounds like ADO vs. ADO.NET is small potatoes here...

一方面,如果没有破损,请不要修理它。但另一方面 - VB6?真?听起来像ADO与ADO.NET这里的小土豆......

I think the issue is more VB vs. VB.NET and then the whole code-base, skill-set, other-non-technical-considerations come into play here.

我认为问题更多的是VB与VB.NET,然后整个代码库,技能组合,其他非技术考虑因素在这里发挥作用。

ADO is unsupported COM-based technology. VB 6.0 is end of life unsupported technology as of March 2008. DAO, RDO, ADO are all technologies that are nearly a decade past their prime.

ADO是不受支持的基于COM的技术。截至2008年3月,VB 6.0是生命周期不受支持的技术.DAO,RDO,ADO都是近十年的技术。

ADO.NET is a modern toolset for data access. In particular, LINQ to SQL and the Entity Framework take data access to new heights.

ADO.NET是一个用于数据访问的现代工具集。特别是,LINQ to SQL和实体框架使数据访问达到了新的高度。

There's nothing wrong with using ADO in legacy VB6 applications. And if these applications are functioning correctly there's no reason to change them.

在旧版VB6应用程序中使用ADO没有任何问题。如果这些应用程序运行正常,则没有理由更改它们。

I don't think anyone programming in .Net will be too tempted to try to use ADO since it feels like such a hack job when you try to. Just let them be.

我认为.Net中的任何编程都不会试图使用ADO,因为当你尝试时感觉就像这样的黑客工作。让他们成为。

Simple answer: don't convince them...

简单回答:不要说服他们......

Have them look at LINQ to SQL (or better yet LINQ to Entities)

让他们看看LINQ to SQL(或者更好的LINQ to Entities)

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

在我的日常工作中能够让人们切换到ADO.NET的最大问题之一是ADO(VB6风格)都是COM,使用ADO.NET可以获得更好的性能。

I heard a rumor that the VB6 runtime will not ship after Windows 7...

我听说有传言称VB6运行时不会在Windows 7之后发布......

I'm guessing if the recordset is still connected and the power goes out on the server, the user would get prompted immediately in their app before they continue to enter data that won't get saved?

我猜测记录集是否仍然连接并且服务器上的电源耗尽,用户会在他们继续输入无法保存的数据之前立即在他们的应用中得到提示?

How about memory garbage collection?

内存垃圾收集怎么样?

Distributing updates is easier in .net.

在.net中更容易分发更新。

I guess if you have a lot of code in VB 6 for winform apps why change? Maybe if you start a new project using VB.NET you can show some other benefits like including multiple tables in a table adapter (Can't say I've taken advantage of that).

我想如果你在VB 6中有很多代码用于winform应用程序,为什么要改变?也许如果你使用VB.NET开始一个新项目,你可以展示一些其他的好处,比如在表适配器中包含多个表(不能说我已经利用了它)。

I prefer ADO.NET myself, but just for balance, there is one advantage of classic ADO over ADO.NET: it is arguably more usable.

我自己更喜欢ADO.NET,但为了平衡,经典ADO优于ADO.NET有一个优点:它可以说更有用。

Our customers found it difficult to use [ADO.NET] because of the extensive initialisation it requires. Even in the simplest scenarios, users are expected to understand complex interactions and dependencies between several types... Note that many of these problems were addressed in the .NET framework 2.0.

我们的客户发现很难使用[ADO.NET],因为它需要广泛的初始化。即使在最简单的场景中,用户也应该理解几种类型之间的复杂交互和依赖关系......请注意,许多这些问题都在.NET framework 2.0中得到解决。

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

由.NET框架的架构师编写,在.NET Framework设计指南第2版第25页中。