Based on the provided information, I assume that there is no other version of the sqlite assembly on the deployment machine besides the one delivered with the application. If that is indeed the case, I would suggest to you two possible solutions - to re-add the reference in Solution Explorer
or to apply an additional <startup>
tag in the <configuration>
section of the .config
The first solution assumes that the sqlite assembly is deployed on the machine but the reference inside the solution is pointing to a place different then the one of the assembly. You can check if this is the case by opening the solution, selecting the reference and reviewing the value of the Path
property in Properties Window
. If the value does not match the actual path to the assembly, you can remove the reference and add it again from the correct place. You can safely rebuild the application after that.
The second solution assumes the target framework of the application is higher than 2.0 and that prevents the usage of the System.Data.SQLite.dll
file which is compiled against .NET Framework 2.0. In this case, you can still utilize the assembly but the following needs to be added in the <configuration>
section of the .config file:
Once you do that, you can rebuild the solution.
I hope this helps. I am looking forward to your feedback.
OpenAccess ORM Q3 2013 Beta is available for immediate download in your account. Get it now
and play with the latest bits. See what's new >>