移动从VB6到.NET最佳策略 [英] Best Strategy for moving from VB6 to .NET

问题描述

我公司拥有万吨的遗产的应用程序都写在VB6。

我们在转换移动VB6应用程序到.NET（3.5专门）。

什么是移动形式VB6到.NET的最佳策略是什么？

注意：下面的更新应该去项目管理和无关的主要问题

  

[更新] ：感谢您的反馈到目前为止
现在有   更多疑问，弹出的

     

  
1. 你将如何分配开发者开发新的应用？
  
2. 如果有一个特殊的一次性升级部门，将其转换   传统的应用程序，以新的？还是应该   每个开发人员参与的   转换过程？
  
3. 如果只有高级开发人员参与的转换？初级   开发商？或者混合？
  

     

这似乎是，我越思考   这个问题，更多的问题只是显示   了起来。

解决方案

显然，这是一大创举，这将涉及大量的工作。
所以，我的建议是把它当作一个很长期的工程。

心中有一个明确的目标，其中涉及如安全性，回弹性，可维护性和应用程序的未来的重大问题。

在此已商定的利益相关者，开发一个原型系统与，测试你的假设，你可以尝试C＃VRS VB.net或MVC VRS Web表单。 我会指定你最好的开发者这一点。

然后启动一个小的遗留系统，构筑了核心组件，您将重新使用在其他领域。
在这个阶段，开始与更多的高级开发人员，但每个人都必须参与进来，并熟悉新的框架。
这将确保每个人都在接受培训的同时，并没有一个人掉队。
根据多少应用程序，你有我会旋转的开发，因此所有系统都可以受益。

此外的所有新的工作必须在.NET语言不VB6来完成。

逐渐转换的遗留应用程序的每一个。 （我只会把它们转换，如果他们正在改变，或者如果有一个明显的好处，以更新它们。）

这应该给你一个坚实的框架使用前进，同时确保用户的功能不会被迁移受阻。

例如：
我在一个公司，有大约40个左右的VB应用程序的工作。
随着时间的推移，我们已经迁移了所有这些C＃和现在（5年后），我们有大约150个C＃应用程序（都在.NET 2）。

这些都有一个共同的框架，使他们易于维护，并延长在必要。

My company has tons of legacy applications that are written in VB6.

We are in transitions from moving VB6 applications to .NET (3.5 specifically).

What would be the best strategy for moving form VB6 to .NET?

NOTE: Below update should go to "Project Management" and has nothing to do with the main question.

[UPDATE]: Thank you for your feedback so far
Now there are more question that pop up are

1. how would you assign developers to develop new applications?
2. Should there be a special one-time upgrade division that will convert legacy apps to new ones? Or should every developer participate on conversion process?
3. Should only senior developers participate on conversion? Junior developers? or mixed?

It seems like, the more I think about this problem, more questions just show up.

解决方案

Clearly this is a major undertaking which will involve lots of work.
So my advise would be to treat it like a very long term project.

Have a clear goal in mind, which addresses major issues like security, resilience, maintainability and the future of your applications.

Once this has been agreed by the stake holders, develop a prototype system to test your assumptions with, where you can try out C# vrs VB.net or MVC vrs Webforms. I would assign your best developers for this.

Then start with one your small legacy systems, and build the core components which you will re-use in other areas.
At this stage, start with your more senior developers, but everyone must get involved and be familiar with the new framework.
This will ensure everyone is trained at the same time, and no one is left behind.
Depending on how many applications you have I would rotate developers, so all systems can benefit.

Also all new work must be done in your .net language not in VB6.

Gradually convert each one of your legacy applications. (I would only convert them if they are changing or if there is a clear benefit to updating them.)

This should give you a solid framework to use going forward, while still ensuring users functionality isn't hindered by your migration.

For example:
I've worked at a company which had roughly 40 or so VB applications.
Over time we have migrated all of these to C# and now (5 years later), we have roughly 150 c# applications (all in .net 2.).

These all share a common framework, making them easy to maintain, and extend where necessary.

这篇关于移动从VB6到.NET最佳策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！