将大型项目从vb6迁移到vb.net [英] Migration of a big project from vb6 to vb.net

问题描述

大家好，

我公司希望将一个大型项目从vb6迁移到vb.net
我在网上阅读了一些文章，但我会问你是否有办法或最佳实践.

vb6项目有一个主要的MDI表单，其中包含许多子表单
我的想法是进行逐步迁移，一次只添加一个表单.可能吗?

我尝试了从vb6到vs2008的大规模迁移，但按照我的设想，被中断了.

多年来，vb6应用程序在架构选择上有些错误:他们使用了许多全局模块，变体和许多第三方控件.

如果您有任何经验，可以给我一些建议吗?

谢谢.

Luke

Hello everyone,

My company want to migrate a big project from vb6 to vb.net
I read some articles on the net, but i would ask to you if there is a way or a best practices to do it.

The vb6 project have a main MDI form with a lot of child forms
My idea is to do a progressive migration, adding just a form at a time. Could be possible?

I tried a massive migration from vb6 to vs2008 , but as i supposed , was interrupted.

The vb6 application have some wrong architectural choices made during the years: they used many global module, variants ,many third-parts controls.

If you had any experience about it, could you give me some suggestion?

Thanks.

Luke

推荐答案

vb语言类似于vb.net，但不相同.如果您认为，有一种简单的方法可以使从vb迁移到vb.net，尤其是当您看到许多
您应该知道，错误的架构选择"不存在.当然，您可以找到翻译器"，但是那样您就在复制错误的体系结构选择".
可能您需要重新编写代码，计划类和接口，删除第三方控件.

The vb language is similar to vb.net but not the same. If you think, there is a simple way to make migration from vb to vb.net, a speccially, when you see many
"wrong architectural choices", you should know, it doesn''t exists. Of course, you can find "translators", but in that way you are copying "wrong architectural choices".
Probably you''ll need to write it again, planning classes and interfaces, removing third-parts controls.

由于VB6对象通常是COM对象，因此您可以使用其中的一些对象在您的新应用程序中.
但是，如果体系结构中有许多功能"，则唯一的机会是完全从头开始编写新的应用程序，或者坚持使用旧的VB.这两个选项都不好.

Since VB6 objects typically are COM objects, you could be able to use some of them in your new application.
But if there are to many "features" in the architecture, the only chances are writing the application completely new from scratch or stick with the old VB. Both options are bad.

这篇关于将大型项目从vb6迁移到vb.net的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！