Learn Entity Framework Core: https://www.learnentityframeworkcore.com/
Entity Framework Core Tutorial: https://entityframeworkcore.com/
Entity Framework 6 Tutorial: https://entityframework.net/
Info
Version: | 2.1.0-preview-20231006.1 |
Author(s): | TheArchitectDev, Timovzl |
Last Update: | Friday, October 6, 2023 |
.NET Fiddle: | Create the first Fiddle |
NuGet Url: | https://www.nuget.org/packages/Architect.Identities.EntityFramework |
Install
Install-Package Architect.Identities.EntityFramework
dotnet add package Architect.Identities.EntityFramework
paket add Architect.Identities.EntityFramework
Architect.Identities.EntityFramework Download (Unzip the "nupkg" after downloading)
Dependencies
- Architect.Identities(>= 1.0.0 && < 2.0.0)
- Microsoft.EntityFrameworkCore(>= 3.1.0)
- Microsoft.EntityFrameworkCore.Tools(>= 3.1.0)
Tags
https://github.com/TheArchitectDev/Architect.Identities
Release notes:
2.1.0:
- The ConfigureDecimalIdTypes() extension method now truncates needless trailing zeros received from the database provider (`123.0` => `123`), as is the case with SQLite.
2.0.0:
- BREAKING: Now targeting .NET 6+, to support new EF Core APIs.
- BREAKING: Now using EF Core 7.0.0.
- BREAKING: No longer referencing the Identities package.
(The current package is still considered an addition to it, but the hard link is gone.)
- BREAKING: Removed ApplicationInstanceIds. (See Identities 2.0.0.)
- BREAKING: Decimal IDs in SQLite may get reconstituted with a one (inadvertent) decimal place, e.g. "1234567890123456789012345678" => "1234567890123456789012345678.0". Detecting and fixing for SQLite is a hassle.
- BREAKING: DecimalIdMappingExtensions's methods have been replaced by modelConfigurationBuilder.ConfigureDecimalIdTypes().
This should be called from DbContext.ConfigureConventions().
- The new extension method handles decimal-convertible types (i.e. value objects) in addition to plain decimals.
- The new extension method also sets DefaultTypeMapping, to achieve appropriate behavior when EF writes things like CAST(). Property mappings alone do not cover such scenarios.
1.0.2:
- Fixed an incompatibility with EF Core 6.0.0+ (caused by a breaking change in EF itself).
- Now using AmbientContexts 1.1.1, which fixes extremely rare bugs and improves performance.
1.0.1:
- Now using AmbientContexts 1.1.0, for a performance improvement.