Conversation
…re 11 (#5324) Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Update documentation to reflect API changes from dotnet/efcore#37993: - SqlServerFullTextIndexBuilder: HasKeyIndex→UseKeyIndex, OnCatalog→UseCatalog, WithChangeTracking→HasChangeTracking, HasLanguage→UseLanguage - FreeTextTable/ContainsTable: columnSelector moved after search text (now optional) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
SamMonoRT
approved these changes
May 12, 2026
There was a problem hiding this comment.
Pull request overview
Updates EF Core 11 (Preview 4) documentation to reflect recent API and tooling changes across SQL Server features, CLI tooling, and provider-facing notes.
Changes:
- Refreshes EF Core 11 “What’s New” content with updated SQL Server full-text APIs, new temporal-period CLR mapping section, new DateTimeOffset/date-time translation notes, and
dotnet efconfig-file support. - Expands provider-facing changes to include
JsonPathtype changes and query test fixture refactoring notes. - Updates SQL Server provider docs (full-text search, temporal tables, function mappings) and CLI reference docs to match the new capabilities and signatures.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md | Adds/updates EF Core 11 preview feature docs (temporal period CLR mapping, DateTimeOffset translations, dotnet ef config file, full-text API signature updates). |
| entity-framework/core/what-is-new/ef-core-11.0/provider-facing-changes.md | Documents new provider-impacting changes (JsonPath type) and test infrastructure refactors. |
| entity-framework/core/providers/sql-server/temporal-tables.md | Adds a new section documenting mapping temporal period columns to CLR properties; updates surrounding guidance. |
| entity-framework/core/providers/sql-server/functions.md | Updates SQL Server function mapping table with new EF Core 11 translations. |
| entity-framework/core/providers/sql-server/full-text-search.md | Updates full-text index configuration and TVF signatures to match the new API names/parameter order. |
| entity-framework/core/cli/dotnet.md | Adds dotnet ef JSON configuration file documentation and supported properties list. |
| ``` | ||
|
|
||
| Notice that SQL Server creates two hidden `datetime2` columns called `PeriodEnd` and `PeriodStart`. These "period columns" represent the time range during which the data in the row existed. These columns are mapped to [shadow properties](xref:core/modeling/shadow-properties) in the EF Core model, allowing them to be used in queries as shown later. | ||
| Notice that SQL Server creates two hidden `datetime2` columns called `PeriodEnd` and `PeriodStart`. These "period columns" represent the time range during which the data in the row existed. By default, these columns are mapped to [shadow properties](xref:core/modeling/shadow-properties) in the EF Core model, allowing them to be used in queries as shown later. Starting with EF Core 11, period columns can also be [mapped to CLR properties](#mapping-period-columns-to-clr-properties) on your entity type. |
| [!code-csharp[NormalQuery](../../../../samples/core/Miscellaneous/NewInEFCore6/TemporalTablesSample.cs?name=NormalQuery)] | ||
|
|
||
| Also, after a normal [tracking query](xref:core/querying/tracking#no-tracking-queries), the values from the period columns of the current data can be [accessed from the tracked entities](xref:core/change-tracking/entity-entries). For example: | ||
| Also, after a normal [tracking query](xref:core/querying/tracking#no-tracking-queries), the values from the period columns of the current data can be [accessed from the tracked entities](xref:core/change-tracking/entity-entries). If the period columns are mapped to CLR properties, you can access them directly on the entity; otherwise, use `EF.Property` to access them as shadow properties. For example: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.