Accepted Solutions
There's no right or wrong. Both languages can do the same thing. You should code in the language that _you_ are the most productive in.
However there's a few things to consider :
1. You'll find way more resources, samples, blog posts and forum posts etc that uses C# than VB.
2. Xamarin doesn't support VB.NET
3. We do tend to focus a little more on C# than VB when it comes to samples and templates (sorry). We don't have infinite resources and by far most of our customers use C#, so we put the effort were it matters to most. And every time we survey what our customers prefer, the VB tribe gets smaller and smaller.
The ArcGIS Runtime Team are mostly C# people too, so we tend to be better at helping with C# responses than VB.NET 
On a more subjective / personal opinion: In contrast to Ted I find C# more readable to VB.NET, because there's less "fluff" around the actual code. Example:
If myObj.CheckCondition Then
'' some code
End If
vs
if (myObj.CheckCondition())
{
// some code
}
I find the Then/End If and all the other verbose statements creates a lot of noise around the much more important logic. It also forces you to put () after a method and not on a property (VB doesn't care), which makes the code very clear whether you're calling a method or a property. But I know that's really just a matter of taste.
There's no right or wrong. Both languages can do the same thing. You should code in the language that _you_ are the most productive in.
However there's a few things to consider :
1. You'll find way more resources, samples, blog posts and forum posts etc that uses C# than VB.
2. Xamarin doesn't support VB.NET
3. We do tend to focus a little more on C# than VB when it comes to samples and templates (sorry). We don't have infinite resources and by far most of our customers use C#, so we put the effort were it matters to most. And every time we survey what our customers prefer, the VB tribe gets smaller and smaller.
The ArcGIS Runtime Team are mostly C# people too, so we tend to be better at helping with C# responses than VB.NET
On a more subjective / personal opinion: In contrast to Ted I find C# more readable to VB.NET, because there's less "fluff" around the actual code. Example:
If myObj.CheckCondition Then
'' some code
End If
vs
if (myObj.CheckCondition())
{
// some code
}
I find the Then/End If and all the other verbose statements creates a lot of noise around the much more important logic. It also forces you to put () after a method and not on a property (VB doesn't care), which makes the code very clear whether you're calling a method or a property. But I know that's really just a matter of taste.
