vb6 迁移到 .net_开发人员为什么不从VB6切换/迁移/转换到VB.NET？

最新推荐文章于 2025-06-20 14:04:12 发布

翻译最新推荐文章于 2025-06-20 14:04:12 发布 · 344 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

原文链接：https://www.hanselman.com/blog/why-dont-developers-switchmigrateconvert-from-vb6-to-vbnet

标签

#java #python #c++ #linux #编程语言

本文探讨了从VB6迁移到.NET所面临的诸多难题，包括技术复杂性、开发者心理障碍及实际操作中遇到的具体问题。文章还分析了迁移路径的不明确性以及这给开发者带来的困扰。

vb6 迁移到 .net

IMHO, it’s because converting (both projects and your mind) to VB6 to .NET is hard.

恕我直言，这是因为将(项目和您的想法)从VB6转换到.NET都很困难。

VB6 existed for one reason and one reason only – to hide the complexities of COM.
VB6存在是出于一个原因和一个原因-隐藏COM的复杂性。
- VB6 was the Matrix, while VB.NET is as powerful as C#. Some folks say, well, while I'm here, I'll just move over to a language with "C" in it, and maybe I'll get more money?
  VB6是Matrix，而VB.NET与C＃一样强大。有人说，恩，当我在这里的时候，我将转到一种带有“ C”的语言，也许我会得到更多的钱？
VB.NET aims to hide nothing – and the exposure is scary to many.
VB.NET旨在不隐藏任何东西–而且这种暴露使许多人感到恐惧。
- VB.NET looks like VB7 - but it's not.
  VB.NET看起来像VB7，但事实并非如此。
VB6 solved the problem of multithreaded Windows Forms by not allowing it.
VB6通过不允许它解决了多线程Windows窗体的问题。
- VB.NET’s WinForms and the BeginInvoke, AsyncResult, and InvokeRequired of it all is complex for anyone, especially a VB6 Mort.
  VB.NET的WinForms以及BeginInvoke，AsyncResult和InvokeRequired对任何人来说都是复杂的，尤其是VB6 Mort。
VB6 is used by places like "Podunk County School District" and "Whatever, Kansas Dept. of Forestry." These are places where Microsoft Access is fine, therefore VB6 is "fine."
VB6在“ Podunk County学区”和“堪萨斯州林业部的任何地方”等地方使用。在这些地方可以使用Microsoft Access，因此VB6很好。
- Until Microsoft explains why VB6 isn’t "just fine" – folks will linger.
  直到Microsoft解释了为什么VB6并不“很好”，人们才会流连忘返。
The Migration Path is not clear and VERY complex – if you did anything funky with OCXs, or if a component vendor didn’t provide you with a migration path, you’re screwed.
迁移路径并不清晰且非常复杂–如果您对OCX进行了一些时髦的操作，或者如果组件供应商没有为您提供迁移路径，那么您将陷入困境。
- The Migration Wizard is an amazing chunk of work, but the 20% edge cases are hard.
  迁移向导是一项了不起的工作，但是20％的边缘情况很难。
Making no decision at all is an implicit decision. Many VB6 developers are paralyzed. That is a decision not to move forward.
完全不做决定是一个隐含的决定。许多VB6开发人员瘫痪了。这是一个不前进的决定。
- Safety first, and safety in numbers.
  安全第一，数量安全。

What do you think? Do you have buddies that are still on VB6? What are they doing it about it? Is VB6SP5 "just fine"? Is VB6 a technology that Microsoft should continue to support?

你怎么看？您是否还有仍在VB6上的好友？他们在做什么呢？ VB6SP5是否“还好”？ VB6是Microsoft应该继续支持的技术吗？

翻译自: https://www.hanselman.com/blog/why-dont-developers-switchmigrateconvert-from-vb6-to-vbnet

vb6 迁移到 .net