Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

Inheritance across namespaces #34

Open
digitalcosmos opened this issue May 1, 2015 · 3 comments
Open

Inheritance across namespaces #34

digitalcosmos opened this issue May 1, 2015 · 3 comments
Assignees

Comments

@digitalcosmos
Copy link

It seems that inheritance and implementations are removed from the class if they're in a different namespace.
Base types such as System.Collections.Generic.List are working but classes from another project are omitted, even tough that project is inside the solution.

Basically, projects are not aware of other projects in the same solution.

Am I doing something wrong, is this intended behavior or is it a functionality that has yet to be added?

@geaz geaz added the bug label May 4, 2015
@geaz geaz self-assigned this May 4, 2015
@geaz geaz added this to the Version 0.9.11 milestone May 4, 2015
@geaz geaz removed the bug label Jul 23, 2015
@geaz
Copy link
Owner

geaz commented Jul 25, 2015

Are you talking about namespaces in the same solution in different projects?
Becuase this works fine here....

@digitalcosmos
Copy link
Author

I'll try to replicate with the latest build, but from what I recall the issue with loading 2 projects from the same solution (in the sdnav file) without referencing the solution itself.

My use case is that I have to build individual documentation for each project in my solution with its dependencies.

@geaz
Copy link
Owner

geaz commented Jul 27, 2015

Thanks, now I get the problem. I will try to replicate this issue and will fix it for the next release.

@geaz geaz removed this from the Version 0.9.11 milestone Sep 29, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants