title: Should I enable or disable dynamic proxies with entity framework 4.1 and MVC3?
body: <p>Could someone offer up some advice or point out some blogs/articles that could help with making this decision? The proxies seem very foreign to me and I'm hesitant to use them. I like the ability to control Lazy Loading by using virtual properties in my model, but that's pretty much all the benefits that I can see. My application is a simple MVC web application and I don't need to wire up any hooks into the context for when the entities experience a changed state. </p>
  
  <p>Anyway, here's my very limited list of pros and cons right now, let me know if I'm off base with any of this. </p>
  
  <p><em><strong>Pros</em></strong></p>
  
  <ul>
  <li>On 'Save' or 'Update',  I get seamless with 'Apply'Changes'</li>
  <li>Lazy-Loading configuration is very easy.</li>
  </ul>
  
  <p><em><strong>Cons</em></strong></p>
  
  <ul>
  <li>Never used proxies before for my entities, this is a change in
  approach that just seems uncomfortable for myself and fellow team
  members. </li>
  <li>Awkward to debug. </li>
  <li>Requires extra code if I want serialize/de-serialize</li>
  <li>On 'Save' or 'Update', the proxy must be the same object that was retrieved from the context.</li>
  </ul>