May 5, 2014 at 6:36 PM
Edited May 5, 2014 at 6:36 PM
Thing is, I've created an utility inspired on AjaxDoc. (It's extensible, framework-agnostic/not locked on AJAX, has sophisticated error catching, etc...)
From there I've created an "OverrideDocSources" plug-in which allows what the name evokes.
(Because I couldn't predict if I would need to override the doc sources generation in the future, I split generation from the plug-in.)
The utility determines namespaces based on folder tree (this is specific to my needs), creates the VSDoc and Reflection XML files, validates them against schema.
So this is the context in which this output has been created. Additionally I use VS2013 as a presentation style.
Regarding Point 1:
The reason I assumed the namespace prefix was not my case specific is the existence of that
Regarding Point 2:
The full member name might be due to my utility input or my plug-in (though I based it on the AjaxDoc plug-in, basically doing the same thing except doc files generation).
I`'m not looking for you to debug it for me. Again, hints are all I'm looking for.