blocks|key|714225|text|你可以看看这篇文章，作为热身，它值得一读：Converting+VB6+to+VB.NET,+Part+I|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|714226|我的建议是只翻译你的用户实际使用的部分，根据他/她的需求添加新功能。|714227|entityMap|0|LINK|mutability|MUTABLE|url|http://dotnet.sys-con.com/node/46335^0|L|W|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You could to take a look into this article, it's worth reading as a warm up: <a href="http://dotnet.sys-con.com/node/46335" rel="nofollow noreferrer">Converting VB6 to VB.NET, Part I</a>

My advice is to translate just pieces your user actually uses, adding new features as he/she demands.

blocks|key|1457546|text|有许多在线代码转换器可以简单地转换语法。以下是一些示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1457547|1457548|http://www.developerfusion.com/tools/convert/vb-to-csharp/|unordered-list-item|offset|length|1457549|http://converter.telerik.com/|1457550|1457551|这些转换器不会处理所有的问题。例如，数组访问在VB中是with+()，与方法访问器相同，而在C#中是[]。这带来了一个问题，因为转换器不知道哪些是方法，哪些是数组。|1457552|显然，最大的问题是旧的VB和.NET之间的差异，即使你翻译了，你也可能会遇到很多关于过时的方法，约束等等的问题。|1457553|我建议在使用代码转换器之前重新评估您的应用程序，这样您就可以对预期的更改有所了解。|1457554|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|1M|0|0|0|T|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@$F|15|G|16|1|17]]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|D]]|X|$5|T|U|V|A|$W|I]]]]

There are many online code converters out there for simply converting syntax. Some examples are:

<ul>
<li><a href="http://www.developerfusion.com/tools/convert/vb-to-csharp/" rel="nofollow noreferrer">http://www.developerfusion.com/tools/convert/vb-to-csharp/</a></li>
<li><a href="http://converter.telerik.com/" rel="nofollow noreferrer">http://converter.telerik.com/</a></li>
</ul>

These converters will not take care of all the issues. For examples, arrays access is with () in VB, same as method accessor, whereas it is [] in C#. This poses a problem because the converters do not know which are methods and which are arrays. 

Obviously, the biggest problem is the differences between old VB and .NET. Even if you do translate, you will likely fall into many problems regarding obsolete deprecated methods, constrictions, etc.

I would suggest to re-evaluate your application before using code converters so that you have an idea of what changes to expect.

blocks|key|2391591|text|这只是一篇关于从VB6迁移到VB.NET和C#的博客文章：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2391592|2391593|+VB6+to+VB.Net+Upgraded+Upgrade+Help+–+Yes,+you+are+not+alone+(in+your+VB6’ness)…+|blockquote|offset|length|2391594|2391595|entityMap|0|LINK|mutability|MUTABLE|url|http://coolthingoftheday.blogspot.com/2010/07/vb6-to-vbnet-upgraded-upgrade-help-yes.html^0|0|0|1|29|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

Just a blog post with some pointers regarding migration from VB6 to VB.NET and C#:

<blockquote>
 <a href="http://coolthingoftheday.blogspot.com/2010/07/vb6-to-vbnet-upgraded-upgrade-help-yes.html" rel="nofollow noreferrer">VB6 to VB.Net Upgraded Upgrade Help – Yes, you are not alone (in your VB6’ness)… </a>
</blockquote>

blocks|key|3799449|text|我会选择C#，因为我更喜欢这种语法。我认为你应该选择你最熟悉的语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3799450|我曾经使用过.Net+VB之前的版本，我也做过一些VB.Net编码，但这两种语言之间的相似性并不足以指导我的选择。|3799451|在任何情况下，它可能更像是一次重写，而不是一个端口，因为在GUI、DB、文件访问等方面存在许多技术差异。|3799452|我希望你现有的产品结构良好，这将有助于这一过程。如果不是这样，那么在移植/重写之前，花时间重构或重构(无论你怎么叫它)都是值得的。|3799453|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|$]]

I would choose C# because I am more comfortable with that syntax. I think you should choose the language you're most at home with.

I used to work with pre .Net VB, and I have done some VB.Net coding, but the similarities between those two languages are not big enough to direct that choice.

In any case, it will probably be more of a rewrite than a port because there are many technological differences in GUI, DB, file access, and so on.

I hope your existing product is structured well, it will help in the process. If it's not, it can well worth the time to refactor or restructure (call it what you will) before porting/rewriting.

blocks|key|1457628|text|在我开始之前:+VB不是一种面向对象的语言...C#和VB.NET是！这一点很重要--开发面向对象与过程化编程完全不同。你可以让你的新系统代码看起来像你现在的样子--但你真的不应该。如果你不想学习面向对象并且改变你的应用程序的运行方式，你不应该开始这个项目，因为你会浪费时间和金钱，而且可能会失败。...After所有你不会把你的笔浸在墨水里很好地补充它-旧的方法是有趣的，但技术存在是有原因的。但我不确定我将面临的挑战。....You应该学习面向对象。之后，有了正确的问题，就很容易得到答案。微软不再支持VB了，你不应该留在后面，特别是当客户要求你移动它的时候。这并不容易--但你别无选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1457629|一种方法是只理解VB代码，然后重写C#或VB中的所有模块.net+....This是唯一的方法-当事情开始崩溃时-你不会指责转换器-你有责任理解系统中的每个函数|1457630|另一种我不知道的方式是基于工具的转换。...others为您提供了工具-它在语法上很好，但在整体功能上有风险|1457631|我想知道你将如何进行这样的转换？您希望使用哪种类型的工具进行转换，以及可能面临的挑战?使用Visio+word+excel或更专业的工具(如UML图表应用程序)+...map您的函数。|1457632|为了简单起见，让我们假设我们要将一个简单的VB转换成一个VB+.net或c#+windows应用程序。...building表单很简单，组件通常更强大|1457633|你更喜欢VB到VB.net的转换还是VB到C#的转换。..。选择C#+vb会让人觉得他们还在vb环境中……C#让你明白你身处一个不同的世界。但重要的是，您将知道Microsoft决定对齐这两种语言，使其具有相同的功能。|1457634|有很好的从一种语言到另一种语言的转换器。|1457635|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Before I start:
VB is not an object oriented language ... C# and VB.NET are!
It's crucial that you bare this deep in your mind - developing object oriented is nothing like procedural programming. You can make your new system CODE look like your current - but you really shouldn't. If you don't feel like learning Object Oriented and change the way your application goes you should not start this project because you'll waste time and money and probably will fail.
...After all you don't dip your pen in ink well to refill it- old methods are interesting but technology is here for a reason.
But I am not sure on challenges that I will be facing.
....You should learn object oriented. After that with the right questions it will be easy to get answers VB is no longer supported by Microsoft and you should not stay behind especially when the customers ask you to move it. It won't be easy - but you don't have a choice.

One method is to just understand the VB code and rewrite all the modules in C# or VB .net
....This is the only way - when things will start falling apart - you will not accuse the convertor - you are responsible to understand every function in your system 

The other way that I am not aware of is the tool based conversion.
...others offered you tools - its good for syntax but risky for overall functionality

May I know how you would approach with such conversion? What type of tools you would prefer for conversion and challenges that you might face?
...map your functions with Visio word excel or more professional tools like UML diagram applications 

For simplicity lets assume that we are going to convert a simple VB to a VB .net or c# windows application. 
...building the forms is easy the components are usually more powerful

Would you prefer VB to VB.net conversion or VB to C# conversion. 
... Choose C# vb make people think they are still in a vb environment... C# makes you understand you are in a different world. Yet it is important that you will know that Microsoft decided to align the two languages to have the same functionality.

There are good convertors from one language to the other.

blocks|key|714191|text|根据我的经验，最好的方法就是重写应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|714192|每次我尝试使用自动转换器时，它都失败得很糟糕。在VB中有很多东西不能很好地转换(比如控件数组)。|714193|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|$]]

In my experience, the best way to do this is to just rewrite the application.

Every time I tried to use an automated converter it failed miserably. There are many things in VB that just don't translate well (like control arrays).

blocks|key|3799515|text|这取决于应用程序的大小、应用程序的图形用户界面和非图形用户界面部分的大小、应用程序使用的外部库/组件，以及您或您的团队更喜欢哪种语言(C#或VB.NET)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3799516|如果您可以在旧的VB应用程序中隔离大量非图形用户界面的代码，那么"VB到VB.NET“的道路通常是更可取的，因为您只需进行很小的更改就可以移植许多旧代码，这一机会并不坏。在所有其他情况下，对于此目的，C#或VB.NET几乎是相同的，因此请选择您在团队中经验最丰富/现有代码最多/最有诀窍的语言。|3799517|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|$]]

It depends - on size of your application, on size of the GUI and non-GUI parts of your application, the external libraries/components your application uses and also which language (C# or VB.NET) you or your team feels more comfortable with.

If you can isolate a lot of non-GUI code in your old VB application, the "VB to VB.NET" road may often be the preferable one, because the chances are not bad that you can port a lot of your old code with only minor changes. In all other cases, C# or VB.NET are almost equal for this purpose, so choose the language you have most experience / most existing code / most know-how in your team.

blocks|key|3799599|text|最好的方法是重写应用程序。我认为使用vb.NET更好，因为语法类似于vb。如果你想尝试转换工具，我推荐VB迁移伙伴。www.vbmigration.com|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3799600|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|$]]

The best way is to rewrite application. I think is better to use vb.NET because syntax is similar to vb. If you want to try a conversion tool I suggest VB Migration Partner. www.vbmigration.com

I have a VB application. Clients wanted to convert that to a .net application. I would like to go ahead and convert that to C# windows application. But I am not sure on challenges that I will be facing.

One method is to just understand the VB code and rewrite all the modules in C# or VB .net

The other way that I am not aware of is the tool based conversion.

May I know how you would approach with such conversion? What type of tools you would prefer for conversion and challenges that you might face?

For simplicity lets assume that we are going to convert a simple VB to a VB .net or c# windows application. 

Would you prefer VB to VB.net conversion or VB to C# conversion. Even if you can answer this question in parts I would appreciate it.

VB to C# or VB.net conversion

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个VB应用程序。客户希望将其转换为.net应用程序。我想继续并将其转换为C# windows应用程序。但我不确定我将面临的挑战。一种方法是只理解VB代码，然后重写C#或VB .net中的所有模块另一种我不知道的方式是基于工具的转换。我想知道你将如何进行这样的转换？您更喜欢哪种类型的工具来进行转换，以及您可能面临的挑战？为了简单起见，让我们假设我们要将一个简单的VB转换成一个VB .net或c

问VB到C#或VB.net的转换
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VB到C#或VB.net的转换EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VB到C#或VB.net的转换
EN