Any difference between a valid C# class name and a valid VB.Net one?

I'm doing some CodeGen work and I want it to use either C# or VB.Net depending on the user selection.

One of the things that is needed is a valid class name - is there any need to implement two versions of this?

I guess the only issue might be language keywords, which would be valid type names in one language but not the other, e.g. Integer or Date would be valid in C# but not in VB, or at least not unescaped.

Spot on - as I discovered when code generation met the Turkish Lira currency code [TRY]... so it looks like I'm going to need to have two language specific functions.