Search:

Well, that's why I started with "JSON doesn't specify type names". You generally can name your objects whatever you want because JSON parsers only look at properties. You can configure some parsers...

What I mean is what I talked about earlier, you can create a name ambiguity.

The reason my "Form" example is immediately aggravating is VB automatically imports System.Windows.Forms into every...

This can be a bad choice still, though.

For example, try creating a project with a class named "Form", and see how fun that is ;)

Names don't matter when you are parsing JSON. JSON represents "objects", and in the JavaScript sense of that word there aren't really "classes" with "names".

Why do you believe the names matter? ...

This is not possible because if you have 2 classes AND a namespace all with the same name, you can create scenarios where it's mathematically impossible for the compiler to understand which of the 3...