11

I created a new console application .net46, install the latest ML and tried a simple LDA. Got the error above. None of the fix that I found on the web seems to work. It is looking for a 4.1.3.0 version of the System.Numerics.Vectors that does not exist.

Marc Engher
  • 111
  • 1
  • 1
  • 3

3 Answers3

17

There is a problem that MSBuild requires version 4.1.3.0 but downloads 4.1.4.0 . You should add

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
        <assemblyIdentity name="System.Numerics.Vectors" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.3.0" newVersion="4.1.4.0" />
    </dependentAssembly>
</assemblyBinding>

to MSBuild.exe.config . It usually located at C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin

I found this bug at Visual Studio 16.8.2 and 16.8.3 .

Vy Do
  • 46,709
  • 59
  • 215
  • 313
0

I think this may be related to this GitHub issue: https://github.com/dotnet/runtime/issues/26370

I think either trying to install the System.Numerics.Vector package as Jon suggested, or maybe update to net472 or .NET Standard 2.0 may help.

Alex S
  • 51
  • 3
0

I got the error in VS 2019 Community Version 16.11.27

could not load file or assembly 'system.numerics.vectors, version=4.1.4.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a' or one of its dependencies. the located assembly's manifest definition does not match the assembly reference. (exception from hresult: 0x80131040)

The projects used to load fine before. Not sure how the issue suddenly came.

Uninstalling and re-installing the same Visual studio version worked for me

jophab
  • 5,356
  • 14
  • 41
  • 60