Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade to Microsoft.EntityFrameworkCore.Sqlite 1.1.0 broke app complaince with WACK
See original GitHub issueEdited by @rowanmiller 11-29-2016
We are shipping a fix for this, but if you hit the issue in the meantime, you can install NuGet 3.5 to resolve the issue http://blog.nuget.org/20161027/Announcing-NuGet-3.5-RTM.html.
Steps to reproduce
Build an app that exists of 3 projects
- the app
- winmd component with background task
- class library to share code between the to other projects
Reference Microsoft.EntityFrameworkCore.Sqlite 1.1.0 in your class library. Run wack tool
The issue
Wack tool will report that the SQLite that is been dragged in by Microsoft.EntityFrameworkCore.Sqlite is not valid for use in UWP. Unallowed api calls to windows.
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (20 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It looks like changing the SQLite package won’t make a difference. minClientVersion isn’t respected by installation by NuGet 3.4.4 on UWP projects. cref https://github.com/NuGet/Home/issues/942.
Closing as we are concerned about unknown side effects of this for various project types etc. NuGet 3.5 will become more widely adopted in the near future.