Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am having difficulty with resolving C# compiler warnings when using an assembly alias in a cref link. Unfortunately, the only feedback that I get from intellisense is ‘Syntax error’. Here is an example of the link [see cref=”global::Namespace.Class.Method”]. From what I can gather, the syntax is correct. The assembly being referenced has ‘global’ set for the alias.
Is this an issue with the compiler? Is there a work-around?
As far as I’m aware,
globalhas the same meaning in documentation comments as in normal code. It’s just a namespace alias which allows you to avoid conflicts between namespace names and type names. See MSDN on the Global Namespace Alias for more details.Note that this isn’t the same as extern aliases which are used when you have two types with the same fully-qualified names, in different assemblies. Your question talking about “different roots” suggests you might be getting confused with extern aliases, but it’s hard to know for sure.