System.Data.SQLite
View Ticket
Not logged in
Ticket UUID: 53993917345be46d2fa35112c3ad055cff7edd98
Title: NuGet sqlite not copy sqlite.dll when use PackageReference in vs2017
Status: Closed Type: Packaging
Severity: Important Priority: Medium
Subsystem: None Resolution: External
Last Modified: 2017-04-03 23:11:32
Version Found In: 3.13.0
User Comments:
anonymous added on 2017-03-16 06:47:00:
use vs2017 create a Classic .NET project and reference sqlite NuGet package use PackageReference. after build sqlite.dll not copy to the output folder

mistachkin added on 2017-03-29 21:35:48:
Does this issue relate to the "System.Data.SQLite.Core" NuGet package or the "sqlite" NuGet package?

anonymous added on 2017-03-31 10:33:43:
I had a similar problem with the SQLite.Interop.dll of System.Data.SQLite.Core with an indirect reference: Project A references SQLite and project B references A but the native dll is not copied to B's output. I solved this by manually setting ContentSQLiteInteropFiles to true in A's .csproj file (as I describe here: http://stackoverflow.com/a/43138364/1771172). Shouldn't this be the default behaviour? As far as I understand, it would also make the CopySQLiteInteropFiles in the NuGet packages's .targets file obsolete.

Florian

mistachkin added on 2017-04-03 23:11:32:
This does not appear to involve the System.Data.SQLite project.  It appears to
refer to the NuGet package for SQLite.

This type of question is better handled on the mailing list:

[/doc/trunk/www/support.wiki]