System.Data.SQLite: View Ticket

Ticket Hash:	cb42aa912604fcf1377936880c385386a863d284
Title:	SQLite.Interop.dll doesn't get coppied to output directory when not a direct dependancy on SDK style projects
Status:	Closed	Type:	Packaging
Severity:	Important	Priority:	Medium
Subsystem:	NuGetPackage	Resolution:	External_Bug
Last Modified:	2020-04-06 21:45:13
Version Found In:	1.0.112
User Comments:
anonymous added on 2020-02-11 20:54:21: This isn't entirly a new issue. However the existing sujested workaround no longer works for SDK style projects because target files from package `build` folders are not imprted from transitive packages Expected behavior When importing a package or referencing a project that depends on System.Data.Sqlite `x86/SQLite.Interop.dll` and `x64/SQLite.Interop.dll` are copied to the output folder Observed Behavior When importing a package or referencing a project that depends on System.Data.Sqlite `x86/SQLite.Interop.dll` and `x64/SQLite.Interop.dll` are not copied to the output folder example files Since Nuget 3.5 there is support for including multiple native libraries. native libraries are resolved based on the RID of the target platform. mistachkin added on 2020-02-20 03:42:48: Based on the issue you linked, this sounds like a bug in NuGet itself.

System.Data.SQLite