Can't you just copy the DLL into the application directory? That just does what the app ought to do (if they don't already).
Then you might have to turn off safe DLL mode to find the correct DLL unless you remove the system one. http://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx#standard_search_order_for_desktop_applications Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Simon Slavin [slav...@bigfraud.org] Sent: Thursday, January 12, 2012 3:59 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] Incompatible versions of SQLite on same system On 12 Jan 2012, at 6:30am, Joe Winograd wrote: > Thanks to both of you for your responses. I'm back to wondering how SQLite > can be effective in the PC world with so many different programs using many > different versions of SQLite. Since all versions are backward compatible, I > was liking Richard's suggestion to get the latest-and-greatest DLL > everywhere, but the DLLs for the two conflicting programs aren't even present. > > Joe, I assume your suggestion to "remove all System.Data.SQLite assemblies > from the GAC and 'convert' them to be application-local" is directed at the > software developers (like HP and Intuit), not at end-users (like me Just to be clear, so is Richard's real suggestion, which is the programmers should statically link to a SQLite library, or to include SQLite source code in their applications and not use a library at all. SQLite is (deliberately designed to be) tiny. Including it all in every application which used it wouldn't use much disk space and would mean problems like the one you reported would never happen: you could have ten apps all expecting different versions of SQLite, and they could all run at the same time with no installation or path problems. Unfortunately, as you noted, this is a decision which can be made only by programmers, not users like you. Oh, and in case you didn't know, Doctor Richard Hipp is SQLite's creator. His advice about it is pretty good. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
