DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Namespace Alias Qualifier in C#

Senthil Kumar user avatar by
Senthil Kumar
·
Aug. 22, 12 · Interview
Like (0)
Save
Tweet
Share
4.44K Views

Join the DZone community and get the full member experience.

Join For Free

the namespace in c# has the following advantages

  • it lets the developers organize their code / classes
  • provides better readability of the code and helps you understand how the code structure is formed, especially in bigger projects.

the namespace alias qualifier in c# lets developers use the alias name instead of the complete namespace name. the advantage of the namespace alias qualifier is that it lets you use the alias name instead of a bigger namespace ( like inner namespaces ) and it also helps to avoid the ambiguous definitions of the classes.

for example

take the below class as an example

using system;
using system.collections.generic;
using system.linq;
using system.text;
using system.threading.tasks;

namespace namespace1
{
    class student
    {
        public string studentname { get; set; }
    }
}
namespace namespace2
{
    class student
    {
        public string studentname { get; set; }
    }
}

when both namespace1 and namespace2 are referenced in the c# file and are trying to create an instance of student, it will cause the “ambiguous name” error as shown in the screenshot below.

to avoid this error, we could use the :: operator to provide an alias name for the namespace and use them accordingly.

using system;
using system.collections.generic;
using system.linq;
using system.threading.tasks;
using system.windows.forms;
namespace windowsformsapplication1
{

    using stud1 = namespace1;
    using stud2 = namespace2;
    static class program
    {
        static void main()
        {
            var obj = new stud1 :: student();
        }
    }
}
dev Advantage (cryptography) Operator (extension)

Published at DZone with permission of Senthil Kumar, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Enterprise, the Database, the Problem, and the Solution
  • Internal Components of Apache ZooKeeper and Their Importance
  • Application Assessment Questions for Migration Projects
  • A ChatGPT Job Interview for a Scrum Master Position

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: