title: 'Get' logic when using automapper
body: <p>This is my Entity:</p>
  
  <pre><code>public class CouponEntity
  {
      public int CouponId { get; set; }
      public int CompanyNumber { get; set; }
      public string Name { get; set; }
      public string FileName { get; set; }
  
      public string CompanySlug
      {
          get
          {
              return COMMONCONSTANTS.URL_COMPANY + "/" + this.CompanyNumber;
          }
      }
  }
  </code></pre>
  
  <p>And the following is my DTO:</p>
  
  <pre><code>public class CouponDto
  {    
      [DataMember]
      public string CompanySlug { get; set; }
      [DataMember]
      public string FileName { get; set; }
      [DataMember]
      public string Name { get; set; }
  }
  </code></pre>
  
  <p>My question is: does using <code>Mapper.Map&lt;IEnumerable&lt;CouponEntity&gt;, IEnumerable&lt;CouponDto&gt;&gt;(lstProducts)</code> greatly affect performance?</p>
  
  <p>I got the following from the AutoMapper creator somewhere on the Internet:</p>
  
  <blockquote>
    <p>DTO is a strict projection of the data model. No business logic in
    mapping 99% "Auto" - restrict customization to minimum Prefer LINQ
    projection</p>
  </blockquote>
  
  <p>So, is this what should be avoided? Is there a better way to accomplish this?</p>