I&#x27;m not sure what you mean exactly but there are already differences between various .net languages there are things you can do with C# that you can&#x27;t really do with VB.NET easily even simple things like bit-wise operators or the fact that you have literal control of overloads in VB which you lack in C# and the list goes on and on.<p>Since the languages them selves work quite differently the interpreter and the CLR can&#x27;t really treat them the same way heck if you make something simple lika a hello world in VB and C# the MSIL won&#x27;t be identical.<p>And with the current nullable support then currently supported Nulleable Type Values for VB.NET and Nullable Types for C# don&#x27;t really work exactly the same way because they still need to conform to the specification of their language first and then to the CLR.