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.
As many have pointed out, I very much doubt there will have been much more work done on the VB6 upgrade wizard. The VB6 upgrade wizard in Visual Studio is actually a cut down version of ArtinSoft's Visual Basic Upgrade Companion.
Upgrading a non-trivial VB6 application is a fairly time consuming task but there are a number of great articles such as this one that can help smooth out the road for you:
Visual Studio 2010 no longer ships a Visual Basic 6 migration wizard tool as mentioned here in the top paragraph. This page links to a list of suggested 3rd party VB6 migration tools.
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.
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.
由于一些基本的语言变化，VB 6 的 Visual Studio 转换充其量是不稳定的。 您可能会发现使用第三方工具（例如 VBMigration Partner）会取得更好的成功
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 VBMigration Partner
发布评论
评论（6）
2008 年肯定没有，如果 2010 年有任何不同，我会感到非常惊讶。VB6
和 VB.net 是完全不同的语言，MS 从未正式认可过除简单应用程序之外的任何内容的自动迁移路线。 迁移路径并不简单。 周围有几家公司提供迁移服务，我没有尝试过，但我的建议是自己管理。
我们目前有几个主要用 VB6 编写的应用程序。 我们的立场是，如果没有充分的理由，现有的工作代码不会迁移到 .net，但所有新代码都必须用 .net 编写（我们实际上选择了 C#），
这意味着如果我们想向现有的 VB6 应用程序必须在 .net 中通过一些互操作来实现该功能。 随着时间的推移，应用程序逐渐变得越来越倾向于 .net，越来越少地采用 VB。 我们现在有 1 个应用程序只有一个很小的 VB6 组件，由于这种逐步迁移方法，其余部分几乎完全在 .net 中。 它对我们来说非常有效。 一旦我们达到了 VB6 部分最少的阶段，我们只需手动转换剩余的代码，无需很高的成本，因为只剩下一点点了。
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.
正如许多人指出的那样，我非常怀疑 VB6 升级向导是否会做更多的工作。 Visual Studio 中的 VB6 升级向导实际上是 ArtinSoft 的 Visual 的精简版本基本升级伴侣。
升级一个不平凡的 VB6 应用程序是一项相当耗时的任务，但是有许多很棒的文章（例如这篇文章）可以帮助您铺平道路：
良好方法论和专业工具的组合，例如 ArtinSoft 和 Code建筑师有望取得成功的结果。
As many have pointed out, I very much doubt there will have been much more work done on the VB6 upgrade wizard. The VB6 upgrade wizard in Visual Studio is actually a cut down version of ArtinSoft's Visual Basic Upgrade Companion.
Upgrading a non-trivial VB6 application is a fairly time consuming task but there are a number of great articles such as this one that can help smooth out the road for you:
A combination of good methodology and professional tools such as those by ArtinSoft and Code Architects will hopefully make for a successful result.
Visual Studio 2010 不再提供 Visual Basic 6 迁移向导工具，如此处所述顶部段落。 此页面链接到建议的第 3 方 VB6 迁移工具的列表。
Visual Studio 2010 no longer ships a Visual Basic 6 migration wizard tool as mentioned here in the top paragraph. This page links to a list of suggested 3rd party VB6 migration tools.
我对此表示严重怀疑，VB10 没有引入任何 VB7、8 或 9 中没有的 VB6 功能，因此他们没有新的理由来更新 2005 年不存在的（可以说是不充分的）升级向导。
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.
由于VS2010仍处于Beta阶段，所以很难说最终产品的表现如何。 现在，看起来迁移代码仍然有点不稳定。
我敢说 VS2010 在导入 VB6 项目这样古老的东西方面不会比以前的版本更好。 很可能，无论发生什么情况，您都必须重写该应用程序的很大一部分才能从 .NET 中获得任何好处。
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.
由于一些基本的语言变化，VB 6 的 Visual Studio 转换充其量是不稳定的。 您可能会发现使用第三方工具（例如 VBMigration Partner）会取得更好的成功
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 VBMigration Partner