Setting to not use fully qualified namespace
Question asked by Work - October 9, 2018 at 12:54 AM
Unanswered
When ghostdoc generates references to other classes it always but the full qualified namespace in which our standard is to shorted as we already have the usings in place. We also use resharper and this is fully controllable, is there somewhere in ghostdoc to do the same?
I'm a .NET Dev Director building Episerver solutions on the cloud using VS, Resharper and Ghostdoc

3 Replies

Reply to Thread
0
Misha Zhutov Replied
Employee Post
Hello,

Thank you for reporting that. Could you please provide us with an example?
0

The major difference

 

If there is a namespace declaration anywhere in the XML file, it is available for that element and all elements in its child tree.

 

Unqualified: If you declare a namespace without using a prefix (unqualified), the default namespace is changed. This means, that all elements without a namespace prefix will be in that specific namespace in the child tree of that element.

 

Qualified: When using qualified namespace declaration, you define a namespace prefix (like a reference) and only those elements will be in that namespace, that have the specified prefix. The default namespace is not changed, therefore elements without prefixes remain in empty namespace.

 

Alexander Randall

Mr. Alexander is providing Dissertation Help to students by his counseling and consultation expertise. 
0
Misha Zhutov Replied
Employee Post
Hi Alexander,

I am aware about what is qualified/unqualified namespace declaration. Sorry, my initial question was about code sample which reproduces the issue. I am not sure I understand if you had problem when generating comment from member signature or when you built help file having XML comments generated by GhostDoc.

Reply to Thread