This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi there, I am attempting to create some UnitTests and use SQLite as the data store. I am on an x64 based system and hence installed the latest x64 System.Data.SQLite from http://system.data.sqlite.org. This is version 1.0.82.0 I have ensured that this is working properly on my system. However, when I try to use the SQLite provider in my config, LightSpeed is looking for 1.0.80.0. When attempting to run migrations I get the following error: Failed: Could not load file or assembly 'System.Data.SQLite, Version=1.0.80.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The system cannot find the file specified. (FileNotFoundException) Is there some way to get x64 1.0.80.0 or else get LightSpeed to link to the version on my system - 1.0.82.0? Ta - Imtiaz |
|
|
You should be able to use a binding redirect to cover this - e.g. Add this into your .config file:
|
|
|
Hi Jeremy, I tried adding the above lines to C:\Program Files (x86)\Mindscape\LightSpeed\Migrations\lsmigrate.exe.config (I created this file) and then once again ran lsmigrate from the command line, but no joy :( I am trying to write UnitTests that use a SQLite DB and hence want the Tests to create a fresh DB using migrations. |
|
|
Have just checked this here - sorry for the delay in responding. Make sure you copy the x64 version of System.Data.Sqlite alongside lsmigrate.exe (I installed the bundle version since this is what we typically ship) and then used the following config file (lsmigrate.exe.config):
Note the specific oldVersion that I applied rather than the wildcard as being different from the earlier block. That sorted it for me here running from the Migrations folder.
|
|