Putting them in your /debug folder was just to troubleshoot. Since it worked, you can move the files to any final folder, and add a reference to System.Data.SQLite.dll
And add your folder to PATH, to find SQLite.Interop.dll For the end-user you can keep it simple and put the files in the same folder as the assembly. On Thu, Apr 18, 2013 at 6:49 PM, Gilles Ganault <gilles.gana...@free.fr> wrote: > On Thu, 18 Apr 2013 13:36:54 -0400, markus diersbock > <mdiersb...@gmail.com> wrote: >>Put SQLite.Interop.dll in the same folder as your VB assembly (ie >>/debug or /release) > > Thanks for the tip. > > But it's kind of a pain to have to copy SQLite.Interop.dll + > System.Data.SQLite.dll in \debug with every new project. > > Why can't we just keep the two files in a central directory, and just > add a reference through "Project > Add Reference"? > > Since the static-bundle version allows this, what is the added value > of the other two (bundle and no-bundle, with dynamic linking to the > VC++ runtime)? > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Markus Diersbock SwingNote Marblehead, MA C 781.929.0693 F 888.654.6068 ------------------------------------ This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential information. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
