The version of the DLL included in the package System.Data.SQLite.Core version is actually

Visual Studio automatically creates assembly redirects in my config files as follows:
      ```xml
<dependentAssembly>
        <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
        <bindingRedirect />
      </dependentAssembly>```

This causes the .Net Framework (I'm using 4.6.2) to try and load the assembly with version from the package, resulting in the following exception:
`Could not load file or assembly 'System.Data.SQLite, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)`

With InnerException:
`Could not load file or assembly 'System.Data.SQLite, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)`

In the Fusion log I saw:
`LOG: Redirect found in application configuration file: redirected to

Which pointed me in the direction of the following workaround:
`<bindingRedirect />`

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.