Replies: 2 comments 4 replies
-
hum normally you could rely on this feature so the different documentations link to each other but because you have duplicate namespaces it will probably fail :/ This is something I will have to fix. |
Beta Was this translation helpful? Give feedback.
-
I am getting the extern-links file to work for my current needs. I have one issue: the namespace appears in each of the extern-links file for each of my projects. DefaultDocumentation gets a collision when trying to import that extern-links file into my main project because of the duplicate: "An item with the same key has already been added". For the sub-projects, is there a way to prevent the namespace entry from being written to the extern-links file without excluding all of the members? |
Beta Was this translation helpful? Give feedback.
-
I have three projects in my solution that all use the same namespace. Is there a way to get them to build into one set of linked markdown files? As is, each builds their separate my.namespace.md file that only has that projects objects.
Project A has a method that uses and object B1 from Project B. Object B1 has a property of type C1 from project C. Is there a way to generate docs that allow linking all the way through from Project A to C.C1?
Beta Was this translation helpful? Give feedback.
All reactions