I believe Your assembly must have a different fully qualified name from the one in the GAC. Otherwise the GAC on is always preferred. This can be done by tweaking the version for example.

By on 4/20/2013 5:55 AM ()

When I do that, I get an error stating, Could not load file or assembly 'FSharp.Core, Version=4.4.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

By on 4/21/2013 7:12 PM ()

Strong name validation fails because you don't have Microsoft's private key corresponding to the token `b03f5f7f11d50a3a`. My guess is you should probably re-sign with your own snk, this will change the PublicKeyToken as well. Not sure it will still work with FSharp.Core though - maybe it is treated specially by the compiler compared to other assemblies.

By on 5/3/2013 5:57 AM ()

You can either add a different assembly reference to your project, or redirect the assembly binding in an associated configuration file. Here is an example of the latter:

1
2
3
4
5
6
7
8
9
10
11
12
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  ...
  <runtime>
    <assemblyBinding appliesTo="..." xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity culture="neutral" name="FSharp.Core" publicKeyToken="b03f5f7f11d50a3a"/>
        <bindingRedirect newVersion="4.0.0.0" oldVersion="2.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>
By on 4/13/2013 2:12 PM ()

I did both. Unfortunately, I keep getting the assembly from the GAC.

By on 4/13/2013 6:01 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper