title: ASP.NET MVC layer separation with SQL Dapper and NHibernate
body: <p>I am working on an ASP.NET MVC application using SQL Dapper for retrieval and NHibernate for CRUD. I am facing some problems with layer separation. </p>
  
  <p>I have repositories say UserRepository which has <strong>public User GetUsersList()</strong> method. Here "User" is an NHibernate entity. The problem here is I need to display a field in the UI which is not present as a property in User like 'HasAltContacts' which I am directly retrieving from an SQL query. </p>
  
  <p>Now, my question is do I need to create separate DTO's and leave these NHibernate entities and build repositories (at least READ METHODS) around these classes?</p>