|Title:||DLL version in package 188.8.131.52 is still 184.108.40.206|
|Last Modified:||2020-05-23 23:52:51|
|Version Found In:||220.127.116.11|
anonymous added on 2020-05-08 07:13:34:
The version of the DLL included in the package System.Data.SQLite.Core version 18.104.22.168 is actually 22.214.171.124.
Visual Studio automatically creates assembly redirects in my config files as follows:
This causes the .Net Framework (I'm using 4.6.2) to try and load the assembly with version 126.96.36.199 from the package, resulting in the following exception:
In the Fusion log I saw:
Which pointed me in the direction of the following workaround:
This results in a working situation.
I'm not sure if it was intended not to change the assembly version with the package version, but I think updating it would have prevented this issue.
mistachkin added on 2020-05-23 23:52:51:
This is by design. The source code was not changed between release 188.8.131.52 and 184.108.40.206. Only the NuGet packages were changed. I have not seen the issue with Visual Studio using binding redirects before; however, it seems like an issue specific to Visual Studio, i.e. as far as I know, there is no requirement for a NuGet package version to exactly match that of the managed assemblies contained within it.