有没有VB应用程序迁移到delphi？
我想听听经典 vb 开发人员将应用程序迁移到 delphi 而不是 vb.net 的经验。 效果如何？ 对于没有转到 vb.net，您感到高兴还是遗憾？
I would like to hear of the experiences of classic vb developers who migrated their applications to delphi rather than vb.net. How has it worked out? Are you glad or sorry that you didn't move to vb.net?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我并不是真正的 vb 开发人员，而是被迫维护一些 vb 应用程序一段时间的 Delphi 开发人员。 我尝试将一个 vb 应用程序迁移到 vb.net，在那次经历之后我再也没有尝试过。 我成功地将几个 vb 应用程序迁移到 Delphi。 这并不容易，而且为一些已使用的 OCX 找到本地 Delphi 替代品成了一件令人头疼的事情（我再也不会依赖我没有源代码的第三方库了。） ，但结果还不错。
但正如上面所说：我是一名经验丰富的Delphi开发人员，因此我不必在迁移vb应用程序的同时学习Delphi。 这确实让事情变得容易多了。
I am not really a vb developer but rather a Delphi developer who was forced to maintain some vb apps for a while. I tried to migrate one vb app to vb.net and after that experience I never tried it again. I successfully migrated several vb apps to Delphi. It wasn't easy and it became a pain in the lower back to find native Delphi replacements for some of the OCXes that had been used (I will never again rely on a third party library for which I do not have the source code.), but it worked out OK.
But as said above: I am an experienced Delphi developer, so I didn't have to learn Delphi at the same time as migrating a vb app. That certainly made it much easier.
我刚刚在 DelphiFeeds 上发现了这个：
面向 Visual Basic 开发人员的 Delphi
帮助将 VB 应用程序（知识和技能）迁移到 Delphi
I just spotted this on DelphiFeeds:
Delphi for Visual Basic developers
Help to migrate VB applications (knowledge and skills) to Delphi
我有一个好朋友不久前从 Classic VB 迁移到 Delphi（早在 .NET 之前）。 他对这个举动非常满意。
他工作的公司用 VB 开发应用程序，他们组建了一个特殊的团队（2 名开发人员）在 Delphi 中创建 Active X 控件，供公司其他人员使用。 此外，当他们无法在 VB 中做到某些事情时，Delphi 团队就会做到。 就在那时，他被介绍给德尔福。
他说，没过多久，Delphi 团队就可以比开发小组的其他成员更快地在 Delphi 中制作应用程序原型（他从未说过有多大，但远远超过两个）。 该公司从未从 VB 转向 Delphi，因为有人认为 VB 是更好的解决方案，尽管有证据表明 Delphi 更强大、更快。
I had a good friend who moved from Classic VB to Delphi a while ago (back before .NET). He was really happy with the move.
The company he worked for made applications in VB, and they put together a special team (2 developers) to create Active X controls in Delphi for the rest of the company to use. Additionally, when there was something that they couldn't do in VB then the Delphi team would do it. That was when he was introduced to Delphi.
He said it didn't take long before the Delphi team could prototype applications in Delphi faster then the rest of the development group (he never said how large, but way more then two) could. The company never made the switch to Delphi from VB because someone was under the impression the VB was a better solution despite the evidence that Delphi was more powerful and faster.
几年来，我在实习年与另一名学生一起工作。 我们在一家非常大的制造公司工作。 他的项目之一是创建一个经典的 VB 应用程序，用于与生产线上的多个摄像机连接并实时分析数据。 在经典的 VB 中，这是一个混乱 - 处理来自单个摄像机（7 个摄像机，24 fps）的单个帧平均需要 1.5 分钟，他无法对其进行优化。
他最终投身于 Delphi 并重新编写了该应用程序，并且运行得非常好。 我最近联系了几个仍然在那里工作的朋友，他们的应用程序已经顺利运行了 3 年。
A few years are I was working with another student on our placement year. We worked for a very large manufacturing company. One of his projects was to create a classic VB app to interface with multiple cameras on a production line and analyse the data in real time. In classic VB this was a shambles - it took on average 1.5 minutes to process a single frame from a single camera (7 cameras at 24 fps) there was no that he could optimise it.
He eventually took the plunge in to Delphi and re-written that app and works fantastically. I've recently been in contact with a few friends who still work there and his app is been running smoothly for 3 years now.
我曾在 VB 和 Delphi 中工作过，而 Delphi (IMO) 的挫败感/限制要少得多。 您应该能够根据需要使用 ActiveX / OCX 控件（尽管我同意其他评论：尽可能避免使用 ActiveX / OCX 控件，并确保拥有完整的源代码）。 我们从 VB 迁移到 Delphi 的应用程序（两个）进展顺利。
I've worked in both VB and Delphi, and Delphi is (IMO) much less frustrating/limiting. You should be able to use ActiveX / OCX controls as needed (though I agree w/other comments re: avoiding there where you can, and being sure ot have full source code). Apps we've migrated from VB to Delphi (two) have gone well.
我确实在两个实例中尝试从 VB 迁移到 Delphi，但不幸的是，我不得不在一个应用程序中中途中止，因为它使用了大量第三方 ActiveX（大部分来自 ComponentOne，少数来自 CodeJoke）。 我们不得不中途放弃，因为我们找不到任何与项目中使用的 ActiveX 具有相同功能的 VCL 组件。
这对我们来说是一场噩梦。 感谢上帝，我们中途放弃并切换到 C#。 令人难以置信的是，我们能够获得 .NET 组件中的所有功能！
我们成功转换的应用程序进展顺利，但我们必须放弃在原始软件中实现的一些功能，因为它们需要在 Delphi 中进行更多工作。
I did try in two instance to migrate from VB to Delphi but unfortunately I had to abort midway in one app as it used a lot of third party ActiveX (most from ComponentOne and a few from CodeJoke). We had to abort midway as we could not find any VCL components having equivalent functionality to the ActiveX used in the project.
It was a nightmare for us. Thank god we aborted midway and switched to C#. It was unbelievable that we could get all the features in .NET component to the ditto!
The app we managed to convert, went well off but we had to get rid of a few features that we had implemented in the original software as they required more work in Delphi.