title: The right ASP.NET boilerplate best practice
body: <p>I just found about the <a href="https://aspnetboilerplate.com" rel="nofollow noreferrer">ASP.NET boilerplate</a> framework for ASP.NET Core applications. The boilerplate is cool, it has all the necessary structure we need in order to create a SOLID proof web application. </p>
  
  <p>My question is that, as per the site I have to create entity models in .Core project, and Dto's in Application project but as I can see these Question, and Answers are different entities but they kept both of them in the same folder and same namespace.</p>
  
  <p>It does not look like a good practice, can anyone tell me is it wrong to keep these related entities in the same namespace/folder or it's ok to do so?</p>
  
  <p><a href="https://i.stack.imgur.com/HvxJ4.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/HvxJ4.png" alt="enter image description here"></a></p>