Kevin and Joe,
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 - I
don't have a clue what the GAC is, nor should I have to in order to run
TurboTax). Regards, Joe
-------- Original Message --------
Subject: Re: [sqlite] Incompatible versions of SQLite on same system
From: Joe Mistachkin <sql...@mistachkin.com>
To: 'General Discussion of SQLite Database' <sqlite-users@sqlite.org>
Date: Wednesday, January 11, 2012 19:06:46
Kevin Benson wrote:
Since the System.Data.SQLite.dll is a mixed assembly (i.e. contains
both managed& native code) in differing versions for x86 versus x64 ,
I wonder if HP meant TurboTax was using, for example, an x86 flavor of
that DLL that conflicts with their (HP) program's use of an x64
flavor?
Also, perhaps their application is binding to the exact version (which is
typical)? One possible solution to this issue is to remove all
System.Data.SQLite assemblies from the GAC and "convert" them to be
application-local (i.e. they would only reside in the same directory as
the application itself); however, this can be difficult, depending on how
the application was written.
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
