将 VB6 应用程序升级到 Visual Basic 2008
我有一个 VB6 应用程序，我想用 Visual Studio 2008 开发它。我遇到的问题是升级向导。启动向导后一切正常。但当解析进程运行时，它会占用 100% 的 CPU 并保持相同的状态：解析表单。
它已经运行了好几天了。
如何以正确的方式迁移应用程序？还有很多其他工具。它们不是免费的，因此无法测试它们是否有效。我对此不确定，因为 Visual Studio 也因解析而挂起。
有什么想法吗？
I've got a VB6 application, and I want to develop it with Visual Studio 2008. The problem I've got is the upgrade wizard. By starting the wizard it's working OK. But when the parsing process is running it take 100% of the CPU and keeps on the same status: Parsing form.
It's running for several days.
How can I migrate the application on a right way? There are a lot of other tools. They are not free, so can't test if they work. I'm not sure about that because Visual Studio is also hanging by parsing.
Any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
听起来升级向导在您的其中一张表单上失败了。 WinForms 与旧的 VB6 表单环境有很大不同，因此您的表单可能无法正确升级。
我建议将旧的 VB6 表单与代码库的其余部分分离，并将它们分成一个单独的项目。然后您应该能够在代码库主体上运行升级向导并从新创建 UI。
这可能是一项艰巨的任务，也可能不是一项艰巨的任务，具体取决于您的 VB6 应用程序以 UI 为中心的程度以及您的 UI 与代码库其余部分的紧密耦合程度。
您是否已通读 Microsoft 的升级准备指南？
http://msdn.microsoft.com/en-us/vbrun/ms788233。 ASPX
Sounds like the upgrade wizard is failing on one of your forms. WinForms is very different to the old VB6 form envinronment, so your forms may not upgrade correctly anyway.
I'd suggest decoupling your old VB6 forms from the rest of the codebase and splitting them out into a separate project. Then you should be able to run the upgrade wizard on the main body of your codebase and create the UI from new.
This may or may not be a huge task, depending on how UI-centric your VB6 application is and how closely-coupled your UI is to the rest of the codebase.
Have you read through any of Microsoft's guidelines for preparing for the upgrade?
http://msdn.microsoft.com/en-us/vbrun/ms788233.aspx
听起来像是升级向导中的错误。确保开发机器安装了所有必需的东西，包括任何第 3 方组件的设计时许可证（您可以编译 VB6 吗？）。如果机器设置正确，我认为您应该联系 Microsoft 技术支持。
关于迁移有很多好的建议，包括这个很棒的 Microsoft 页面，以及很多StackOverflow 上的讨论。
Sounds like a bug in the upgrade wizard. Make sure the development machine has everything necesary installed, including design-time licenses for any 3rd party components (can you compile the VB6?). If the machine is set up properly I think you should contact Microsoft technical support.
There's lots of good advice on migrating, including this great Microsoft page, and a lot of good discussion on StackOverflow.