title: ASP.NET Core Routing with 2 Referenced Projects
body: <p>I've added a second project to an existing solution and am running into a bit of an issue with routing requests.</p>
  <p>When I initially add the second project, there is no problem with routing.</p>
  <p>However, I have a DB Context in the original project that I'd like to use from the second.  It is when I add the project reference that my issue manifests.</p>
  <p>The issue is that I am getting ambiguous routing requests, so I need to find a way to distinguish requests, for example, to the Home Controller.</p>
  <p>Be advised, I use attribute routing.</p>
  <p>I've come up with a few workarounds:</p>
  <ul>
  <li>Copy the DB Context into the second project. This has obvious shortcomings and is the least attractive solution, but it will work.</li>
  <li>Set up routes with some distinguishing prefix, i.e. &quot;/proj2Home&quot;, etc.  While crude, this is the least objectionable and is straight-forward to implement. It does mandate a route value for every Url of the second project but I could hold my nose on that.</li>
  <li>I've considered using Middleware but it looks like the error is coming from UseRouting() (although I'm not 100% on this) so I'm not sure what I can do at that point.</li>
  </ul>
  <p>Does anyone know of some sort of build-in mechanism to accomplish this?</p>