title: How are dotnet core assemblies resolved in an asp.net core app hosted in IIS
body: <p>We have an asp.net core application running on kestrel hosted in IIS on windows server 2008.</p>
  
  <p>This application uses several base components and we are used to just install these components in the GAC and use assembly redirects to point all applications on the same server to the latest version of these components.</p>
  
  <p><em>Everything runs fine when we deploy the application including all the necessary assemblies.</em></p>
  
  <p>However, when we apply a <strong><em>redirect</em></strong> on a dotnet core assembly (we apply the redirect <em>in the  <strong>[app].exe.config</em></strong>, not the web.config) to a version that is installed in the <strong><em>GAC</em></strong>, we get a type exception ... </p>
  
  <blockquote>
    <p>Application startup exception: <strong>System.TypeLoadException: Could not
    load type</strong> 'my.company.namespace.coolest.component.helpers'</p>
  </blockquote>
  
  <p>Curiously enough, the redirects for the plain old dotnet4 assemblies work when specified in the <em>[app].exe.config</em>, only the redirect for the dotnet core assembly fails.</p>
  
  <p>So, I'm now wondering. How are dotnet core assemblies resolved? Which locations are searched for ? </p>
  
  <p>(And ultimately, is it possible at all to redirect to a dotnet core assembly in the GAC)</p>
  
  <p>[<strong>EDIT 23/OCT/2017:</strong> 
  Doh... turns out the latest dotnet core assembly from our team was bad.. 
  so to answer my own question.. yes, assembly redirects (when specified in [app].exe.config) for dotnet core assemblies targeting full .net framework do work and ARE also searched from the GAC]</p>