It is a very personal thing but I prefer VB. The languages are very similar but the IDE support for VB appears better. VB is more verbose but C# seems to make up for that with empty space (page heights seem longer with C#).
If I take out type safety I can get a character count which is only slightly more than equivalent Python code. Although gap would increase with overall code length.
Type:
Public Class XX
Implements IExternalCommand + Return (and the rest is autocomplete).
Type:
public class xx : IExternalCommand + Return (then I get an error / question asking me what to do next)
I don't know if there is an option for that in C# i.e. a 'do the obvious thing next for me' option? I probably don't use it long enough to find out.
I think the IDE for VB is getting worse though due to shared components. I'm sure intellisense used to ignore case but someone has made it so you must practically type the case correctly to get what you are looking for faster. Case sensitivity is a C# thing but even in C# it makes no sense to compare by case in a suggestions list when the autocorrect will eventually change to what is selected anyway. Some C# puritan has tinkered with that and not seen the bigger picture.
However C# always appears to have less future uncertainty. We should all go back to C++ really, the original option for cross platform support.