Commented Unassigned: Layouts, views and partials with same name in different assemblies [162]

In my separate MVC project with RG, there are "parent" layouts, views and partials. In my main MVC project(s), I have "child" layouts/views/partials, which derive from them.

If these files have the same names and/or paths, *IIS itself crashes*. I want to use the same names and paths, as it makes sense when defining common assets which are then extended in my main/client projects.

Is this by design, or a bug? ...it seems like a bug, because I think having them in different assemblies should be enough to differentiate between them.

How do I deal with this? There are similar problems here and on StackOverflow going back many years, but I can't find a solution.
Comments: Yes, strange indeed. I attached a debugger onto IIS, and when it crashes it's because of either an `OutOfMemoryException` or a `StackOverflowException`. So basically, there is some kind of recursion going on, because of the identical names and paths. Changing the names or the paths avoids the problem. But makes our namespaces weird. I'd really like to use the same names and paths in our common and client assemblies. Just don't know how to do that...