title: Is it necessary to manually add <AutoGenerateBindingRedirect> metadata to the Core project file to correctly reference assemblies?
body: <p>I'm using Visual Studio 2013 and MvvmCross to create an Android application using Portable Class Libraries.</p>
  
  <p>I notice in my first view model, CatalogViewModel, some code is highlighted as not referencing the correct assemblies or unable to be resolved (the code builds fine even with these issues).</p>
  
  <p><img src="https://i.stack.imgur.com/iD50k.png" alt="enter image description here"></p>
  
  <p>Examining the .NET Portable Subset assembly in the Object Browser shows various System assemblies included (2.0.5.0 v2.0.50727 &amp; v4.0.30319, 4.0.0.0, 5.0.5.0). Automatic binding redirection for assemblies in .NET Framework 4.5.1 can be <a href="http://msdn.microsoft.com/en-us/library/2fc472t2%28v=vs.110%29.aspx" rel="nofollow noreferrer">enabled or disabled</a> by adding this line to the .csproj file.</p>
  
  <pre><code>&lt;AutoGenerateBindingRedirect&gt;true&lt;/AutoGenerateBindingRedirect&gt;
  </code></pre>
  
  <p>or</p>
  
  <pre><code>&lt;AutoGenerateBindingRedirect&gt;false&lt;/AutoGenerateBindingRedirect&gt;
  </code></pre>
  
  <p>This seems to solve the referencing and redirection issues in the IDE. I haven't found any information about this manual modification to the Core project file in any of the MvvmCross info online I reviewed so I wanted to post a question here to see if anyone had some information or best practices.</p>
  
  <p><img src="https://i.stack.imgur.com/8j1XG.png" alt="enter image description here"></p>