title: Best approach for a large intranet structure with multiple nested applications
body: <p>So on the current system (running off of the .net 3.5 framework) the way it was made was there is a project for the main intranet site. This page uses a dll to load the menu &amp; layout. Then there are a bunch of separate applications (different solutions) that use this same dll to load the site structure and then get deployed as a new iis site. The menu has links to each of these applications and essentially it creates one large intranet site.</p>
  
  <p>The idea is to recreate the intranet which I have been tasked with. I will be using .net core 2.1 and a mvvm (or mvc) structure. So my question is what is the best way to go about this? I am not totally convinced that the current system uses the best approach and I kinda want to get out of the dll hell that the current system uses (there are lots of dlls not just for the layout). As for the layout and its re-usability what is the best approach for this? Should there be separate solutions for each internal project and how would they reuse the site layout if so? Or should it be one HUGE solution with multiple projects? Or what other approaches could be recommended?</p>