Am 27.02.2013 15:28, schrieb Gilles Ganault:
On Tue, 26 Feb 2013 19:45:27 -0500, Kevin Benson
<kevin.m.ben...@gmail.com> wrote:
Right, but while the first DLL will be found since it's now part of
the project (Project > Add Reference), the wiki doesn't say that this
doesn't take care of the other DLL.
http://www.mail-archive.com/sqlite-users@sqlite.org/msg73039.html
Good to know, although creating an .\x86 or .\x64 doesn't seem to add
anything as compared to simply putting the two DLLs in the
application's directory.
Speaking of which, why is the no-bundle version (two DLLs) to be
prefered to the bundle version (single DLL)? It solves this issue.
I still didn't find any info on the web about what the difference is.
The wiki says: "All the "bundle" packages contain the
"System.Data.SQLite.dll" mixed-mode assembly. These packages should
only be used in cases where the assembly binary must be deployed to
the Global Assembly Cache for some reason (e.g. to support some legacy
application on customer machines). "
Anyone knows more?
Thank you.
I asked Joe Mistachkin a while back the same. Here's what he replied:
Am 21.09.2012 00:35, schrieb Joe Mistachkin:
Bernd wrote:
Could you elaborate on why I should avoid doing as I do at the moment?
The mixed-mode assembly contains native code for one platform as well as
the managed code. This prevents the same application from being easily
deployed on both x86 and x64.
I suppose if you only ever deal with one processor architecture on all the
target machines, it's just fine to use the bundled packages.
Also, mixed-mode assemblies are not supported by Mono or the .NET Compact
Framework.
--
Joe Mistachkin
_______________________________________________
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
