hardrain

Item #1:
Project Reference > DLLClass1
Project Properties > Imports > Namespace.Namespace2
- In Code Behind:
* Dim NewClass1 As New Class1

Item #2:
Project Reference > DLLClass1
- In Code Behind:
* Dim NewClass1 As New Namespace.Namespace2.Class1

* What will be better? Item #1 or #2?, Does MS have an article for this? (I
need proof for this matter, about their performance, advantages and
disadvantages.)

Thanks in Advance!

sgt_pinky

Both are identical. Namespaces and classes have their own signatures, so the IDE/compiler will tell you if there are two classes/methods with the same name.

For example, if you program Direct3D and DirectSound, both Namespaces have the object called 'Device'. If you Import both Namespaces, then the IDE will get really upset and put blue squiggly lines all over the shop when you try and declare a New Device.

hardrain

Thanks, I think in performance it will be the same.
But to avoid the ambigous name for classes declarations, it should be Item #2.

sgt_pinky

To avoid Repetitive Strain Injury I use Item #1.