I guess you know the way you can define aliases with the using statement:
using SWF = System.Windows.Forms;
Then you can use the shortcut
SWF to reference a type in the namespace. In C# 1, the syntax was like this:
SWF.Button button = new SWF.Button();
Obviously this could be ambiguous, because there could have been any kind of different identifier in scope called SWF. To get rid of this ambiguity, C# 2 introduced the
:: qualifier. So now you’ll write the same thing differently:
SWF::Button button = new SWF::Button();
So, the identifier to the left of the
:: qualifier (called the namespace alias qualifier, by the way) defines the namespace that is searched for the identifier to the right of the qualifier. This is where
global comes into play: this is an identifier you can use if you want to look only at the global namespace. For example, to make absolutely sure that a reference to a class called String can only ever mean (the framework standard)
System.String, you could put something like this:
global::System.String mystring = new global::System.String('x', 10);
Sorry, this blog does not support comments. Why not?
I used various blog hosting services since this blog was established in 2005, but unfortunately they turned out to be unreliable in the long term and comment threads were lost in unavoidable transitions. At this time I don't want to enable third-party services for comments since it has become obvious in recent years that these providers invariably monetize information about their visitors and users.
Please use the links in the page footer to get in touch with me. I'm available for conversations on Keybase, Matrix, Mastodon or Twitter, as well as via email.