but anyways, yeah, creating C# was a little weird since VB.NET does pretty much the same. Just the taste I guess
Your right to some degree, it is a matter of taste. But there is a good side effect of using the C# language over VB.Net. Sure they produce pretty much the same thing and have the same abilities (minus or plus a few features), but when you use C#, you are using a syntax that is in use by C++ and Java (plus or minus a few small differences). This means that it is a hell of a lot easier to switch over to these languages when they are needed.

For example, I haven't used Java in over a year and a coworker asked me for some help because she was learning Java and had no idea of what she was doing. I thought I wouldn't be able to help much without fumbling around a lot. I was completely wrong. I might as well have been writing C# code when I was helping her. I whipped out her complete assignment without having to reference anything at all for help. It felt good to be able to EASILY switch over to another language after not using it for over a year and produce what was needed in 10 minutes. This was a direct result of me using C# lately. If I would have stuck with VB.Net I wouldn't have been able to help her at all.

Just my thoughts on the language argument.... Sure VB.Net and C# are almost the same thing, but there are other benefits that you have to look at also.