Vikas Yadav

 Profile Answers by Vikas Yadav 

• Apr 5th, 2008

 

Aliases can be useful in the case if you are using a lenthy namespace.You can create an aliase for namespace and can acess its classes via alias.

On the negative side it can cause some conflicts if you declare any class with same name in that scope.But finally it can be resolved through scope resolution operator.

PeterVH

• Aug 19th, 2011

 

Well, it is needed if for some reason you have conflicting names. Silly example, but suppose you declare a variable with the name DateTime, and to be very funny (sarcasm) you also define a variable named System.

When you later on want the normal DateTime.Now you are in trouble. First off, DateTime will be your local variable. Okay, you can try System.DateTime but that won't work because you also have a variable named System.

So what to do? Here comes the alias to save the day (cfr example)

Code
using DateTimeAlias = System.DateTime;


 


namespace WindowsFormsApplication4


{


    public partial class Form4 : Form


    {


        public Form4() { InitializeComponent(); }


 


        private void button1_Click(object sender, EventArgs e)


        {


            // April fools? It is an example okay, not very likely to happen in real life..


            const int System = 5;


            const int DateTime = 5;


 


            Debug.WriteLine("But I can still get the Now value by using my alias! " + DateTimeAlias.Now);


        }


    }


}

LordAlex

 Profile Answers by LordAlex 

• Nov 3rd, 2011

 

C# provides a set of predefined struct types called the simple types. The simple types are identified through reserved words, but these reserved words are simply aliases for predefined struct types in the System namespace.
{sbyte, byte, short, ushort, int, uint, long, ulong, and char}