C＃vs VB.NET - 我是否应该为未来的员工从VB.Net进行重构？ [英] C# vs VB.NET - Should I go through the effort to refactor from VB.Net for future employees?
问题描述
我花了至少两年的时间从事一个大型项目，并用VB.NET编写了全部内容，我关注三点。
1人们不认真对待VB.NET。 （他们认为这是马车等等）
2.更多人了解C＃。 （是吗？）
3.如果我重建它，我可以将一些流程简化为更少的形式。
I不知道C＃。我对VB.NET相当不错。为公司而言，为了其他人的利益将80％重构为项目是否值得花时间和精力？
I have spent at least 2 years working on a large project and have coded the whole thing in VB.NET and I am concerned with three points.
1. People don't take VB.NET seriously. (They think it's buggy, etc.)
2. More people understand C#. (True?)
3. Should I rebuild it, I may be able to streamline some of the processes into fewer forms.
I don't know C#. I am fairly good with VB.NET. Is it worth the time and effort to refactor 80% into a project for other people's benefit as far as a company is concerned?
推荐答案
感谢您的回复。我同意你的观点。从业务的角度来看，它让我觉得谨慎地重构C＃。
Thanks for your reply. I agree with your points. From a business perspective, it has struck me as being prudent to refactor to C#.
我认为，这是有道理的。
然而，它有与重构无关（ https://en.wikipedia.org/wiki/Code_refactoring [ ^ ]）。这是翻译。
你知道你可以完全自动翻译，质量很好，如果你只是构建所有程序集然后用不同的语言反编译它使用开源的ILSpy？请参阅我过去的答案，我在其中解释了这些步骤：代码解释，C＃到VB.NET [ ^ ]。
I my opinion, it makes certain sense.
However, it has nothing to do with "refactoring" (https://en.wikipedia.org/wiki/Code_refactoring[^]). This is translation.
Do you know that you can do translation fully automatically, with good quality, if you just build all the assemblies and then decompile it back in different language, using, say, open-source ILSpy? Please see my past answer where I explain the steps: Code Interpretation, C# to VB.NET[^].
这篇关于C＃vs VB.NET - 我是否应该为未来的员工从VB.Net进行重构？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
