title: How to avoid deploying endpoints in dependent projects net core 6?
body: <p>I have two projects <strong>baseApi</strong> and <strong>myOtherApi</strong> , both legacy projects are in net6.0</p>
  <p><strong>baseApi</strong> is a basic API deployed as <em><a href="http://myBasicApi.com" rel="nofollow noreferrer">http://myBasicApi.com</a></em> and it have some endpoints:</p>
  <blockquote>
  <p>&quot;/groups/opened&quot;<br/>
  &quot;/users/whitelist&quot;</p>
  </blockquote>
  <p><strong>myOtherApi</strong> is a complementary API deployed as <a href="http://myOtherApi.com" rel="nofollow noreferrer">http://myOtherApi.com</a> and it have other endpoints:</p>
  <blockquote>
  <p>&quot;/trucks/available&quot;<br/>
  &quot;/invoices/{groupId}&quot;</p>
  </blockquote>
  <p><strong>myOtherApi</strong> depends of <strong>baseApi</strong> (because it share its models classes), it's Ok.</p>
  <p>But the issue is when I deploy <strong>myOtherApi</strong> it deploys endpoints of <strong>baseApi</strong> (i.e. <a href="http://myOtherApi.com/users/whitelist" rel="nofollow noreferrer">http://myOtherApi.com/users/whitelist</a> responses OK), and it's wrong because <strong>baseApi</strong> endpoints shuoldn't be exposed in this project (baseApi is only for admin clients)</p>
  <p>Are there some config or another way to avoid expose these external endpoints on <a href="http://myOtherApi.com" rel="nofollow noreferrer">http://myOtherApi.com</a>?</p>