Some tests in the Entity Framework Core codebase require features only available on Microsoft SQL Server 2016 Developer Edition or higher. Since most developers only have Microsoft SQL Server 2016 LocalDB (and even then only because it was installed by Visual Studio), it can be troublesome to run these tests.
This post demonstrates the different ways you can customize the migrations history table in EF Core.
In Entity Framework 4.1+ we would validate entities before sending them to the database. See Entity Framework Validation to read more about it.
Say what you’d like about XML vs. JSON. (I like YAML) I’m still very excited about NuGet’s deeper integration with MSBuild. That’s because MSBuild is so much more than its antiquated file format. It’s an execution engine that enables you to define configuration and sets of data, transform that data, then process it using various tasks.
One of the frequently asked questions about Microsoft.Data.Sqlite is: How do I encrypt a database? I think that one of the main reasons for this is because System.Data.SQLite comes with an unsupported, Windows-only encryption codec that can be used by specifying
HexPassword) in the connection string. The official releases of SQLite, however, don’t come with encryption.
I recently added a feature to Microsoft.Data.Sqlite to enable shareable in-memory databases. These are in-memory databases that can be accessed by multiple connections. Just remember to keep at least one connection open or the database will disappear.
Channel 9’s Seth Juarez had a chance to invade our team room and capture some rare footage of the EF magic unicorns in their natural habitat. I got to show some of the improvements we’ve been making to Migrations. Here’s the video.
subscribe via RSS