Jiwa 8

[SBarnes]

Given it appears that the c# compiler seems stronger on type checking than vb I would choose c# everytime for that reason alone as I would prefer not finding errors at runtime.

It would be insteresting to rerun the survey on the forums and see what the results would be today as I think the original question was asked in 2015.

[pricerc]

Given it appears that the c# compiler seems stronger on type checking than vb

That's only true if you've got the relevant compiler switches wrong on your VB compiler.

You should always have:
Option Strict On
Option Explicit On
Option Infer On

Which can be changed per-file, or at a project level.

[pricerc]

conversion quality is worse (e.g. Recent c# features aren't well supported)

It's the last sentence that was of concern for us.

Ahh. They've never had *great* VB support in that converter.

There are other options, but they all struggle with "recent C# features", not helped by Microsoft's slightly weird attitude towards VB - deciding that there would be "no new features" in VB, despite the reasonably active vblang repo on GitHub that had more than a few good ideas, and a few pull requests from people willing to contribute.

Some of those suggestions were, however, incorporated into C# ...

c'est la vie.

The former PM of VB (Anthony D Green) is pretty active on the VisualBasic Discord and has some interesting observations.

Going back to my earlier observation, I still "don't blame you". Jiwa has to make technical decisions that also make commercial sense - if you provided a "C# to VB" converter, you'd need to also support it. And if it is only half-baked, it would be more work to support.

But well done for not killing VB altogether - which I have seen elsewhere and not understood.

For the stuff I do, which involves business-related code that I sometimes need "non-programmers" to be able to read, VB has been helpful, because it can be easy to follow even if you're not a programmer. I've been known to talk someone through editing VB code over the phone. I wouldn't want to try that with C#.