Going from C# to VB should be easy. Since BASIC has always been about a more human-readable syntax. And I am certainly capable of reading, interpreting, and converting C#, similar to my understanding French or Spanish, it's just that I can't "speak" it fluently.
The whole .NET model is based on language-independance. I am actually promoting this concept. By "exploratory," I mean that we are all working with pre-release code. We have been given license to see what the capabilities are for this library. I'm promoting the capabilities of this library to not be restricted or limited.
"Supported languages" is what it says. Official support will be provided for the C# language. Being an MVP, you might have some official stance you have to take, I don't know. However, since this is only a
CTP, nothing is truly official yet.
I didn't say you've insulted me. Some of my bitterness is from the whole "VB programmers are sloppy" mentality that has grown steadily as programmers convert to C# from Java or C. It's an unfair stereotype.
As far as full release timing, you probably know better than I, since you have access to some MVP resources. I don't know what the outstanding issues are with Zune XNA. I haven't hit any showstoppers, and I can only think of some general improvements. I think it's in great shape as it is so I can't see why they couldn't get it in, unless the Zune application team is too swamped to do the integration.
So, are we in agreement that an experienced VB developer shouldn't have any problem developing for Zune? However, an inexperienced VB programmer who would either have trouble writing in a language-neutral manner or would have difficultly managing two projects (despite that the C# project is practically maintenance-free) should keep it simple and use C# exclusively.