We are pleased to present below all posts tagged with 'SQLite'. If you still can't find what you are looking for, try using the search box.
Some notes on adding and removing migrations in Entity Framework core.
EF Code First approach (Create class/es first)
Entity Framework, in Code First Manner, can auto-generate the scaffolding for accessing a database from an app from an app’s model class. In a previous blog I covered some issues wrt using Entity Framework Core with a Universal Windows (Platform) app with a Sqlite backend database. The entities are specified as classes in in a .Net Core class project separate to the app project (within the same solution). The issue addressed in that blog was a problem referencing the class library from the UWP project. This blog revisits the same topic with an emphasis upon the steps required to implement an EF Core backed UWP app.
It’s well known that Microsoft made a very clear choice regarding the use of a DBMS within embedded products, from smartphones (Windows Phone) to tablets (Surface WinRT) via the devices based on Windows Embedded Compact 2013; this choice has a precise name and it is SQLite ! From WEC7 to WEC2013 : SQL Server Compact removed ! As far as Windows Embedded Compact, the change was made from version 7 to 2013, even removing the "SQL Server Compact" feature within Platform Builder Catalog Items (in the "Core" features related to the SYSGEN_SQLCOMPACT variable) through which it was easy to add support for this DBMS into the operating system image. Also, in the official MSDN documentation of .Net Compact Framework 3.9 it is described the removal of SQL Server Compact support within the framework itself and the use of SQLite is reported as a possible "workaround". At this point, we just have to accept the choice made by Microsoft and explore how you can use SQLite in our embedded systems. SQLite : nati ...
For Windows Embedded Compact 2013, the SQL Compact database component is deprecated leaving Compact 2013 without a viable local database resource.