Preview.7 docs

[AndriySvyryd]

No description provided.

[Copilot]

Pull request overview

Updates EF Core 11 preview documentation to reflect new Cosmos DB provider behaviors and tooling improvements.

Changes:

• Document Cosmos DB provider modernization (System.Text.Json-based materialization, __jObject removal, and unmapped-property round-tripping changes).
• Add guidance and breaking-change details for undefined values in Cosmos projections.
• Document -NoBuild support for Package Manager Console migrations commands.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md	Adds “What’s New” entries for Cosmos serialization changes, undefined projection behavior, and -NoBuild in PMC.
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md	Adds multiple new breaking-change entries (Cosmos + model/config changes) and updates the Microsoft.Data.Sqlite breaking changes section.
entity-framework/core/providers/cosmos/unstructured-data.md	Clarifies __jObject availability (EF Core 10 and earlier) and links to EF Core 11 breaking changes.
entity-framework/core/providers/cosmos/querying.md	Adds a new section explaining undefined projection behavior and mitigation patterns (IsDefined, CoalesceUndefined).
entity-framework/core/cli/powershell.md	Documents -NoBuild for Add-Migration and Update-Database.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (2)

entity-framework/core/providers/cosmos/unstructured-data.md:17

• This page now contains EF Core 11-specific guidance, but the front-matter ms.date is still 11/05/2019. On Microsoft Learn, ms.date is expected to reflect the last significant content update; please bump it so the page isn't shown as outdated.

> [!NOTE]
> The `"__jObject"` shadow property was removed in EF Core 11. See [Breaking changes in EF Core 11](xref:core/what-is-new/ef-core-11.0/breaking-changes#cosmos-jObject-removed) for details.

In EF Core 10 and earlier, it was possible to access properties not tracked by EF Core through a special property in [shadow-state](xref:core/modeling/shadow-properties) named `"__jObject"` that contained a `JObject` representing the data received from the store and data that will be stored:

entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md:763

• In this section you're referring to the NuGet package SQLitePCLRaw.core elsewhere (e.g. the XML snippets below), but here the prose uses SQLitePCLRaw.Core. To avoid confusion, please use the same package ID casing consistently.

The `SQLitePCLRaw.bundle_e_sqlcipher`, `SQLitePCLRaw.bundle_sqlite3`, `SQLitePCLRaw.bundle_winsqlite3`, `SQLitePCLRaw.bundle_green`, and `SQLitePCLRaw.bundle_e_sqlite3mc` packages are no longer updated by the SQLitePCLRaw maintainer. They are not compatible with `SQLitePCLRaw.Core` 3.0 and later, so applications that directly reference any of these packages alongside `SQLitePCLRaw.Core` 3.x will encounter conflicts. Applications should migrate to the recommended alternatives to avoid future breakage.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (1)

entity-framework/core/providers/cosmos/unstructured-data.md:40

• The admonition type here is WARNING, but the text is purely informational/historical (it just states that "__jObject" existed only in EF Core 10 and earlier and was removed in EF Core 11). Using a warning callout may mislead readers into thinking there's an actionable hazard in current versions; consider downgrading this to a NOTE (the breaking-change warning is already covered above).

> [!WARNING]
> The `"__jObject"` property was part of the EF Core infrastructure. It exists only in EF Core 10 and earlier, and has been removed starting with EF Core 11.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (1)

entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md:811

• The statement "throws … when any part of a projection evaluates to undefined" is broader than the behavior described elsewhere (e.g., naked projections using SELECT VALUE can still silently skip undefined results). To avoid misleading readers, please scope this to anonymous-type/DTO projections (which is what the surrounding paragraph discusses).

Previously, when projecting scalar properties via optional navigations where a document path was absent (resulting in an `undefined` value in Cosmos DB), behavior was inconsistent: single-property anonymous type projections silently dropped those results, while multi-property projections threw a cryptic exception.

EF Core 11 now consistently throws an `InvalidOperationException` when any part of a projection evaluates to `undefined`. Use <xref:Microsoft.EntityFrameworkCore.CosmosDbFunctionsExtensions.IsDefined*> to filter or <xref:Microsoft.EntityFrameworkCore.CosmosDbFunctionsExtensions.CoalesceUndefined*> to provide fallbacks:

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.