blocks|key|1306701|text|我严重怀疑这一点，VB10没有从VB6引入任何VB7、8或9中没有的功能，所以他们不会有新的理由来更新他们在2005年不存在的升级向导(可以说是不充分的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1306702|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would seriously doubt it, VB10 has not introduced any features from VB6 that were not present in VB7, 8 or 9, so there would be no new reasons for them to update their (arguably inadequate) upgrade wizard that did not exist in 2005.

blocks|key|1306750|text|由于VS2010仍处于测试阶段，很难说最终产品的表现如何。现在，看起来迁移代码仍然有点麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1306751|我要冒险地说，在导入像VB6项目这样古老的东西方面，VS2010不会比以前的版本更好。无论发生什么情况，您都可能不得不重写该应用程序的很大一部分，以便从.NET中获得任何好处。|1306752|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Since VS2010 is still in Beta, it's hard to say how the final product is going to perform. Right now, it looks like the Migration code is still a little rocky.

I'm going out on a limb and saying that VS2010 isn't going to be any better at importing something as old as a VB6 project than previous versions. Chances are, no matter what happens, you're going to have to re-write a significant portion of that application to get any benefit out of .NET anyway.

blocks|key|1521859|text|2008年肯定没有，如果2010年有什么不同，我会非常惊讶。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1521860|VB6和VB.net是完全不同的语言，微软从未正式认可过用于简单应用程序以外的任何东西的自动迁移路线。迁移路径并不平凡。周围有几家公司提供迁移服务，我还没有尝试过，但我的建议是自己管理它。|1521861|我们目前有几个应用程序主要是用VB6编写的。我们的立场是，现有的工作代码没有充分的理由不会迁移到.net，但所有新代码都必须用.net编写(我们实际上选择了C#)。|1521862|这意味着，如果我们想要在现有的VB6应用程序中添加一个新功能，该功能必须在.net中实现，并具有一定的互操作性。随着时间的推移，应用程序变得越来越.net，越来越少VB。我们有一个应用程序，现在只有一个很小的VB6组件，其余的几乎完全在.net中，这要归功于这种渐进的迁移方法。它对我们来说工作得很好。一旦我们达到了VB6部分最小的阶段，我们就可以简单地手动转换剩余的代码，而不需要很高的成本，因为只剩下很少的代码了。|1521863|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It certainly hasn't in 2008 and I'd be very surprised if it's any different in 2010.

VB6 and VB.net are totally different languages, and MS has never officially endorsed an automatic migration route for anything beyond simple applications. The migration path is non-trivial. There are several companies around that offer migration services, I haven't tried them but my advice would be manage it yourself.

We currently have several apps that are written largely in VB6. Our position is that existing working code is not migrated to .net without a good reason, but all new code must be written in .net (We've actually chosen C#)

What this means is that if we want to add a new feature to an existing VB6 app the feature must be implemented in .net with some interop. Gradually over time are apps are becoming more and more .net and less and less VB. We have 1 app that just has a tiny VB6 component now and the rest is almost entirely in .net thanks to this gradual migration approach. It has worked very well for us. Once we reach a stage where the VB6 portion is minimal, we simply manually convert the remaining code without high cost because there is only a tiny bit left.

blocks|key|1306883|text|由于一些基本的语言变化，VB6的Visual+Studio转换充其量也是参差不齐的。你可能会发现使用像VBMigration+Partner这样的第三方工具会更成功|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1306884|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vbmigration.com/^0|1F|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Visual Studio conversion of VB 6 is spotty at best, due to some of the fundamental language changes. You might find better success looking at a third party tool like <a href="http://www.vbmigration.com/" rel="nofollow noreferrer">VBMigration Partner</a>

blocks|key|1306911|text|Visual+Studio2010不再提供Visual+basic6迁移向导工具，如顶部段落中提到的here。本页面链接到建议的第三方VB6迁移工具列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1306912|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/vbasic/ms788233^0|1E|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Visual Studio 2010 no longer ships a Visual Basic 6 migration wizard tool as mentioned <a href="http://msdn.microsoft.com/en-us/vbasic/ms788233" rel="nofollow">here</a> in the top paragraph. This page links to a list of suggested 3rd party VB6 migration tools.

Has anyone migrated a VB6 project to .Net with Visual Studio 2010?

I have tested the migration in VS2005, but the resulting .Net code was so messed up, that we decided not to migrate to .Net. So has the VS2010 migration wizard been improved over the wizard in VS2005 or VS2008?

VB6 migrating to .Net with Visual Studio 2010

有没有人用Visual Studio2010将VB6项目迁移到.Net？我已经在VS2005中测试了迁移，但是生成的.Net代码非常混乱，所以我们决定不迁移到.Net。那么，与VS2005或VS2008中的向导相比，VS2010迁移向导是否得到了改进？

问使用Visual Studio2010迁移到.Net的VB6
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Visual Studio2010迁移到.Net的VB6EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Visual Studio2010迁移到.Net的VB6
EN