C# and VB are just the syntax you use for working with the. If the problem is you're worried it's complex, it's not, really. And when you ask questions in VB, you'll get fewer answers, because the people who answer will be only the C# developers who don't mind reading VB and speaking in its terms. In that way, I feel like you're going to have to learn C# anyway.
#Monogame for visual studio 2015 code#
You can ask people to help you translate them, but that's slower than copying code directly. The examples you'll read will be in C#, and require you to transcribe and translate them before you gain any value. I'm almost certain Mono has a VB compiler.
Now, if you're sufficiently motivated, there should be no good reason why you can't work with Monogame in VB. I don't know if that was a bad thing, but I at least understand why it felt bad. I understand now, more than ever, why VB6 fans feel betrayed: the language went from something really special to being "as good as the other language". It's not different from C# in any significant way such as "easier to learn" or "has RAD tooling". I've always had a fondness for it, but it lost the battle. That's a hard thing to write as someone who, 13 years ago, first cut his teeth on professional development in VB. NET project, the only good reason to use VB at this point is "I have to, because my boss said so."
If you know VB, you know C# and vice versa. There's almost no reason to list VB as one's primary language today. I don't hate it, but right now it's not really filling a niche like it used to. The answer is really hard to explain without making it sound like I hate VB.