C# vs VB.NET - Should I go through the effort to refactor from VB.Net for future employees?

Question

1.00/5 (1 vote)

See more:

.NET4.5

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?

Posted 19-Oct-15 14:44pm

Infinity2Solutions

Add a Solution

Comments

Sergey Alexandrovich Kryukov 19-Oct-15 21:20pm

It depends on "who are those people". It's not just about the quality of the languages and compilers. Note that C# carries great culture behind it, and VB.NET carries VB tradition of a language for hobbyists, which hardly was adequate to this role when it was created. And even when VB.NET gets professional qualities, people will keep not taking is seriously, just because of this tradition. I don't think it's buggy or something. Besides, C# is standardized, and VB.NET was never planned for standards, as far as I know. So, think by yourself.
As to the "effort"... 1) All .NET languages have common identical core, in terms of semantics, 2) you cannot afford not knowing C# well, if you are a .NET developer. In real life, you just got to know it.
—SA

Infinity2Solutions 19-Oct-15 21:24pm

Thanks for your reply. I agree with your points. From a business perspective, it has struck me as being prudent to refactor to C#.

Sergey Alexandrovich Kryukov 19-Oct-15 21:53pm

...And it might be much easier to do than you thought so far. Please see Solution 1.
—SA

PIEBALDconsult 19-Oct-15 22:42pm

If it ain't broke; don't break it.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-10-19T15:52:00

Infinity2Solutions wrote

Thanks for your reply. I agree with your points. From a business perspective, it has struck me as being prudent to refactor to C#.

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[^].

—SA