.net – 从VB6.0升级的最佳开发工具

自动转换是比重写更好的选择.这是一个常见的陷阱,开始乐观地重写一个大型软件,在旧架构中修复一些众所周知的缺陷,早日取得良好的进展,然后陷入你多年来一直认为理所当然的功能陷入困境.在这一点上,您的管理层开始变得神秘莫测,一切都会变得非常不舒服.

……这是微软的一篇博文,agrees with me：

Many companies I worked with in the early days of .NET looked first at rewriting driven in part by a strong desire to improve the underlying architecture and code structures at the same time as they moved to .NET. Unfortunately many of those projects ran into difficulty and several were never completed. The problem they were trying to solve was too large

这个优秀的Microsoft page推荐两个第三方迁移工具,比(不再是available)内置的VB.NET升级向导 – Artinsoft和CodeArchitects VBMigration更好.我相信他们对常见的第三方控件和DLL有一些支持 – Artinsoft支持these.值得联系他们的依赖列表. VBMigration有一个free tool,它将列出依赖项,正是出于这个原因.也值得联系原始供应商,希望.NET等价.

微软页面还说：

Performing a complete rewrite to .NET is far more costly and difficult to do well [than converting] … we would only recommend this approach for a small number of situations.

在Stack Overflow上有比VB.NET开发人员更多的C#开发人员,所以你可能会得到几个推荐C#的答案.从历史上看,微软也倾向于在.NET的新部分的代码示例方面更热情地支持C#等等.但微软现在assure我们做了：

Both [C# and VB.NET] are first-class programming languages that are based on the Microsoft .NET Framework,and they are equally powerful.

因此,无论您是要选择C#还是VB.NET,都是个人决定. Artinsoft工具声称它可以将VB6转换为C#.

编辑：我刚刚通过编程网站上的广告找到了另一个产品 – NewCode！

我的判断是,该网站并不像我上面写的两个竞争对手那么详细.这可能是不公平的.微软爱尔兰blogged的一些人关于他们 – 我认为他们的总部设在爱尔兰.显然,该工具将您的VB6转换为DSL,然后转换为VB.NET Winforms,C#,WPF,Java ……