{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3261","labels_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3261/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3261/comments","events_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3261/events","html_url":"https://github.com/aspnet/EntityFramework/issues/3261","id":108896537,"number":3261,"title":"Provide NuGet packages without sqlite3.dll","user":{"login":"rainman-63","id":10222560,"avatar_url":"https://avatars.githubusercontent.com/u/10222560?v=3","gravatar_id":"","url":"https://api.github.com/users/rainman-63","html_url":"https://github.com/rainman-63","followers_url":"https://api.github.com/users/rainman-63/followers","following_url":"https://api.github.com/users/rainman-63/following{/other_user}","gists_url":"https://api.github.com/users/rainman-63/gists{/gist_id}","starred_url":"https://api.github.com/users/rainman-63/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rainman-63/subscriptions","organizations_url":"https://api.github.com/users/rainman-63/orgs","repos_url":"https://api.github.com/users/rainman-63/repos","events_url":"https://api.github.com/users/rainman-63/events{/privacy}","received_events_url":"https://api.github.com/users/rainman-63/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-29T15:37:52Z","updated_at":"2015-09-29T15:37:52Z","closed_at":null,"body":"The EntityFramework.Sqlite NuGet package has a dependency on the Microsoft.Data.Sqlite NuGet package, which contains the sqlite3.dll.  If we use a custom sqlite3.dll (distributed either as an Extension SDK or as a NuGet package) with the EntityFramework.Sqlite NuGet package, the build will fail because there are 2 sources for the sqlite3.dll.\r\n\r\nWhen using a custom version of the sqlite3.dll, you have a few options: \r\n\r\n1)\tCopy the custom version of the sqlite3.dll into the .nuget\\packages\\Microsoft.Data.Sqlite\\1.0.0-beta6\\runtimes folders.  \r\n\r\n2)\tManually deleting the sqlite3.dll from the .nuget\\packages\\Microsoft.Data.Sqlite\\1.0.0-beta6\\runtimes folders.\r\n\r\n3)\tCreate a custom nuget package, with all the EntityFramework.Sqlite dependencies manually added. Not a big fan of doing this, especially since the packages are already built with the small problem of providing the sqlite3.dll.\r\n\r\nAll of these solutions are okay for a single developer but with multiple dev teams to contend with; several build servers which are shared with other projects; automated builds; etc... they're not very maintainable.\r\n\r\nIf the Entity Framework NuGet packages did not contain the sqlite3.dll, this would allow users to use either a custom version, a version that was previously downloaded as an Extension SDK, or a NuGet package.\r\n\r\nIf you have any suggestions or input on alternative solutions, we would be greatly appreciative.\r\nThanks!\r\n"}}