RubixRevenge
commented
6 years ago Thinking about this some more. I could potentially follow this model.
For example, when browser is in a Sitemap View of Website 1, the user sees (in pseudo-code).
-
Sitemap of Website 1:
@Html.MvcSiteMap().SiteMap() -
Other Project Sitemaps Process the sitemaps from the other projects, pre-pending the correct server/folder names.
@Html.MvcSiteMap().SiteMap()
It would be better if they could see the union of both link sets, so that the same order of links could be presented no matter which website you are in.
Forgive me if the answer to this question already exists in the documentation, but I have not been able to locate it or recognize the answer if I saw it.
I use MvcSitemapProvider (version 4 for .NET MVC 5) to handle my site navigation from a single sitemap file. However, my MVC 5 project has grown to be very large. I would like to split the single application into different solutions because each of the areas really are (mostly) independent of each other.
In other words, I want to refactor my project from this:
Solution "One Mega MVC Project"
to this:
Solution "Website 1" -- MVC 5 App #1 -- One MvcSitemapProvider sitemap file with links to this and links in the other projects
Solution "Website 2" -- MVC 5 App #2 -- One MvcSitemapProvider sitemap file with links to this and links in the other projects
Solution "Website 3" -- MVC 5 App #3
-- One MvcSitemapProvider sitemap file with links to this and links in the other projects
...More solutions
Having an identical sitemap file per project looks to me like breaking the "do not repeat yourself" rule. Is there a way for me to have only one sitemap file that all the projects read from, so I only need to maintain a single sitemap file?