Is it good practice to use namespace like a variable???

Hemant Mehra

Is it good practice to use namespace like a variable???

using CommonEntities = HEPL.Common.UIModel.Entities;

using HEPL.Common.UIModel.Entities;

which one is good practice in above code?

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes12y ago
The only really good reason for using the first of those:

using CommonEntities = HEPL.Common.UIModel.Entities;

is if that particular namespace contains a type (SomeClass say) whose name clashes with a type in another namespace you're importing or which you've written yourself.

Instead of having to write out HEPL.Common.UIModel.Entities.SomeClass you can then abbreviate it to CommonEntities.SomeClass to distinguish it from the other SomeClass in your project.

jitendra kumar12y ago

using HEPL.Common.UIModel.Entities; This will be better approach. Because respective
this namespace, classes, methods, property can be accessed directly in the code. 
If it to assign to using variable, then it takes the separate place in memory.
It causes the performance issue of the application.

Pradeep Shet12y ago

Hi hemant,
Both are same things but according to me,

using HEPL.Common.UIModel.Entities; 

is a good practice but if you want to use classes of specific namespace and for better readability
like without doing mouseover on class you want to know the namespace to which any particular class 
belong then go for namespace like a variable.

Hope this helps you, if yes mark it answered.