Preview.7 docs

entity-framework/core/cli/powershell.md

@@ -2,7 +2,7 @@
 title: EF Core tools reference (Package Manager Console) - EF Core
 description: Reference guide for the Entity Framework Core Visual Studio Package Manager Console
 author: SamMonoRT
-ms.date: 11/08/2024
+ms.date: 08/03/2026
 uid: core/cli/powershell
 ms.custom: sfi-ropc-nochange
 ---
@@ -122,8 +122,9 @@ Parameters:
 | Parameter                          | Description                                                                                                             |
 |:-----------------------------------|:------------------------------------------------------------------------------------------------------------------------|
 | <nobr>`-Name <String>`</nobr>      | The name of the migration. This is a positional parameter and is required.                                              |
-| <nobr>`-OutputDir <String>`</nobr> | The directory use to output the files. Paths are relative to the target project directory. Defaults to "Migrations". |
+| <nobr>`-OutputDir <String>`</nobr> | The directory to use for the output files. Paths are relative to the target project directory. Defaults to "Migrations". |
 | <nobr>`-Namespace <String>`</nobr> | The namespace to use for the generated classes. Defaults to generated from the output directory.  |
+| <nobr>`-NoBuild`</nobr>            | Don't build the project before running the command. Intended to be used when the build is up-to-date. Added in EF Core 11. |
 
 The [common parameters](#common-parameters) are listed above.
 
@@ -319,6 +320,7 @@ Updates the database to the last migration or to a specified migration.
 | <nobr>`-Add`</nobr>                 | Creates a new migration and applies it to the database in a single step. Uses Roslyn to compile the migration at runtime. When specified, a migration name is required and provides the name for the new migration. Added in EF Core 11. |
 | <nobr>`-OutputDir <String>`</nobr>  | The directory to put migration files in. Paths are relative to the target project directory. Requires `-Add`. Added in EF Core 11. |
 | <nobr>`-Namespace <String>`</nobr>  | The namespace to use for the generated migration classes. Requires `-Add`. Added in EF Core 11. |
+| <nobr>`-NoBuild`</nobr>             | Don't build the project before running the command. Intended to be used when the build is up-to-date. Added in EF Core 11. |
 
 The [common parameters](#common-parameters) are listed above.
 

entity-framework/core/providers/cosmos/querying.md

@@ -2,7 +2,7 @@
 title: Querying - Azure Cosmos DB Provider - EF Core
 description: Querying with the Azure Cosmos DB EF Core Provider
 author: SamMonoRT
-ms.date: 09/19/2024
+ms.date: 08/03/2026
 uid: core/providers/cosmos/querying
 ---
 # Querying with the EF Core Azure Cosmos DB Provider
@@ -213,6 +213,51 @@ Note that <xref:Microsoft.EntityFrameworkCore.CosmosQueryableExtensions.FromSql*
 
 For more information on SQL querying, see the [relational documentation on SQL queries](xref:core/querying/sql-queries); most of that content is relevant for the Azure Cosmos DB provider as well.
 
+## Undefined values in projections
+
+In Azure Cosmos DB, a document property can be `undefined` — this happens when the property is simply not present in the JSON document. This can occur when navigating through an optional relationship that is absent for some documents, or when a property was added to the model after existing documents were written.
+
+Starting with EF Core 11, when any part of an anonymous type or DTO projection evaluates to `undefined`, an `InvalidOperationException` is thrown with the message "A part of the projection was undefined, use the coalesce operator to handle possible undefined values." See the [breaking changes documentation](xref:core/what-is-new/ef-core-11.0/breaking-changes#cosmos-undefined-projection) for details on upgrading from EF Core 10 and earlier.
+
+To handle undefined values in projections, use <xref:Microsoft.EntityFrameworkCore.CosmosDbFunctionsExtensions.IsDefined*> to filter out documents where a value is missing:
+
+```csharp
+var results = await context.Entities
+    .Where(x => EF.Functions.IsDefined(x.Associate!.NestedAssociate!.Id))
+    .Select(x => new { x.Associate!.NestedAssociate!.Id })
+    .ToListAsync();
+```
+
+Alternatively, use <xref:Microsoft.EntityFrameworkCore.CosmosDbFunctionsExtensions.CoalesceUndefined*> to substitute a default value for any property that could be `undefined`:
+
+```csharp
+var results = await context.Entities
+    .Select(x => new { Id = EF.Functions.CoalesceUndefined(x.Associate!.NestedAssociate!.Id, Guid.Empty) })
+    .ToListAsync();
+```
+
+### Naked projections and SELECT VALUE
+
+A _naked projection_ — where a single value is projected directly without wrapping it in a DTO or anonymous type — is translated using `SELECT VALUE` in Cosmos DB SQL. As a result, any documents where the projected value is `undefined` are **silently skipped** and not included in the results:
+
+```csharp
+// Naked projection - translated as SELECT VALUE, undefined results are silently omitted
+var ids = await context.Entities
+    .Select(x => x.Associate!.NestedAssociate!.Id)
+    .ToListAsync();
+```
+
+In contrast, any top-level instantiation in the projection (anonymous type, DTO, entity, or complex type) does **not** use `SELECT VALUE`. When a part of such a projection is `undefined`, an `InvalidOperationException` is thrown as described above.
+
+If silently skipping undefined results is not the desired behavior, wrap the projected value in an anonymous type or DTO to get a consistent error instead:
+
+```csharp
+// Wrapped in an anonymous type - does not use SELECT VALUE, throws if undefined
+var results = await context.Entities
+    .Select(x => new { x.Associate!.NestedAssociate!.Id })
+    .ToListAsync();
+```
+
 ## Function mappings
 
 This section shows which .NET methods and members are translated into which SQL functions when querying with the Azure Cosmos DB provider.

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

@@ -2,7 +2,7 @@
 title: Azure Cosmos DB Provider - Working with Unstructured Data - EF Core
 description: How to work with Azure Cosmos DB unstructured data using Entity Framework Core
 author: AndriySvyryd
-ms.date: 11/05/2019
+ms.date: 08/03/2026
 uid: core/providers/cosmos/unstructured-data
 ---
 # Working with Unstructured Data in EF Core Azure Cosmos DB Provider
@@ -11,7 +11,10 @@ EF Core was designed to make it easy to work with data that follows a schema def
 
 ## Accessing the raw JSON
 
-It is possible to access the properties that are not tracked by EF Core through a special property in [shadow-state](xref:core/modeling/shadow-properties) named `"__jObject"` that contains a `JObject` representing the data received from the store and data that will be stored:
+> [!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:
 
 [!code-csharp[Unmapped](../../../../samples/core/Cosmos/UnstructuredData/Sample.cs?highlight=21,22&name=Unmapped)]
 
@@ -35,10 +38,7 @@ It is possible to access the properties that are not tracked by EF Core through
 ```
 
 > [!WARNING]
-> The `"__jObject"` property is part of the EF Core infrastructure and should only be used as a last resort as it is likely to have different behavior in future releases.
-
-> [!NOTE]
-> Changes to the entity will override the values stored in `"__jObject"` during `SaveChanges`.
+> 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.
 
 ## Using CosmosClient