C# not as strict as VB.NET Option Strict On

Question

I work in both C# and VB.NET and I've noticed that in C# you can do stuff like: UInt32 x = 0; but in VB.NET, with Option Strict On, you can't do: dim x as UInt32 = 0 I had always thought that C# was about as strict as VB.NET with Option Strict On, but it appears that VB.NET with Option Strict On is actually stricter than C# - has anyone else noticed this?