Hi Joe, Think of it this way. I have software A, which is the software I am writing an add-in for. The way add-ins are loaded is by selecting all the required libraries for the application. These items are then stored in a repository on a server through that software. I cannot control the storage structure of software A, thus all the libraries required are stored in a single folder location. This prevents me from using the typical method you describe (which would typically work for a standard application).
So my thought was to take the interop and have it as an embedded resource in my library and on initial run extract it into the client side add-in folder. The add-in folder gets created by the software A that I am writing the add-in for. Does that help clear up what I am running into? Christopher Sonon | Application Engineer | CEPDM | CWPDM | CSWST ModernTech |1626 Downtown West Blvd. | Knoxville | TN | 37919 | USA Phone: 865.934.5329 | Fax: 865.934.5353 "If you want to improve, be content to be thought foolish and stupid." Epictetus "If we find ourselves with a desire that nothing in this world can satisfy, the most probable explanation is that we were made for another world." CS Lewis Solidworks Technical Support | [email protected] | 1.877.553.9001 Live Technical Support | Monday - Friday 8-5 Eastern Time | ModernTech GoToAssist -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joe Mistachkin Sent: Wednesday, October 10, 2012 10:13 AM To: 'General Discussion of SQLite Database' Subject: Re: [sqlite] SQLite.Interop Chris Sonon wrote: > > I cannot do this as there is no "project library". Essentially I > select some > libraries and they get "loaded" into the software that I am > programming to. > So basically everything needs to sit in one repository. > The native library pre-loading feature handles pre-loading of the SQLite interop assembly itself. I'm not sure what you mean by "project library" in this context. There are two libraries (or pieces) necessary to use System.Data.SQLite: 1. The managed components, which are always contained in System.Data.SQLite.dll. 2. The native components, which in this case are contained in SQLite.Interop.dll. This DLL can be pre-loaded automatically by the native library pre-loading feature present in the System.Data.SQLite.dll as long as it resides in an "x86" or "x64" sub-directory of the directory where the System.Data.SQLite.dll file is located, which is typically the application directory. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
