dotnet · BillWagner · Nov 10, 2022 · Nov 7, 2022 · Nov 9, 2022 · Nov 9, 2022
diff --git a/.whatsnew.json b/.whatsnew.json
@@ -10,7 +10,7 @@
         "maximumNumberOfArticles": 3,
         "tocParentNode": "What's new",
         "repoTocFolder": "docs/whats-new",
-        "indexParentNode": "Find .NET updates",
+        "indexParentNode": "Latest documentation updates",
         "repoIndexFolder": "docs/whats-new"
     },
     "areas": [

diff --git a/.whatsnew.release.json b/.whatsnew.release.json
@@ -0,0 +1,81 @@
+{
+    "$schema": "https://whatsnewapi.azurewebsites.net/schema",
+    "docSetProductName": ".NET",
+    "rootDirectory": "docs/",
+    "docLinkSettings": {
+        "linkFormat": "relative",
+        "relativeLinkPrefix": "../"
+    },
+    "inclusionCriteria": {
+        "labels": [
+            "label:\":checkered_flag: Release: .NET 7\""
+        ],
+        "maxFilesChanged": 100,
+        "minAdditionsToFile": 1
+    },
+    "navigationOptions": {
+        "maximumNumberOfArticles": 4,
+        "tocParentNode": "What's new",
+        "repoTocFolder": "docs/whats-new",
+        "indexParentNode": ".NET release updates",
+        "repoIndexFolder": "docs/whats-new"
+    },
+    "areas": [
+        {
+            "names": [ "." ],
+            "heading": "Home"
+        },
+        {
+            "names": [ "architecture" ],
+            "heading": "Architecture guides"
+        },
+        {
+            "names": [ "azure" ],
+            "heading": "Azure SDK for .NET"
+        },
+        {
+            "names": [ "csharp" ],
+            "heading": "C# language"
+        },
+        {
+            "names": [ "desktop-wpf" ],
+            "heading": ".NET Core desktop"
+        },
+        {
+            "names": [ "framework" ],
+            "heading": ".NET Framework"
+        },
+        {
+            "names": [ "fsharp" ],
+            "heading": "F# language"
+        },
+        {
+            "names": [ "core/compatibility" ],
+            "heading": ".NET breaking changes"
+        },
+        {
+            "names": [ "core", "fundamentals", "standard" ],
+            "heading": ".NET fundamentals"
+        },
+        {
+            "names": [ "iot" ],
+            "heading": ".NET IoT libraries"
+        },
+        {
+            "names": [ "machine-learning" ],
+            "heading": "ML.NET"
+        },
+        {
+            "names": [ "spark" ],
+            "heading": ".NET for Apache Spark"
+        },
+        {
+            "names": [ "visual-basic" ],
+            "heading": "Visual Basic language"
+        },
+        {
+            "names": [ "orleans", "dotnet-orleans" ],
+            "heading": "Microsoft Orleans"
+        }
+    ]
+}
diff --git a/api/index.md b/api/index.md
@@ -3,12 +3,12 @@ description: "Learn more about: .NET API browser"
 layout: ApiBrowserPage
 hide_bc: true
 title: .NET API browser
-quickFilterColumn1: net-6.0,netframework-4.8,netstandard-2.1
-quickFilterColumn2: aspnetcore-6.0,efcore-6.0,xamarin-forms
+quickFilterColumn1: net-7.0,netframework-4.8,netstandard-2.1
+quickFilterColumn2: aspnetcore-7.0,efcore-6.0,xamarin-forms
 quickFilterColumn3: azure-dotnet,ml-dotnet,spark-dotnet
 ms.topic: landing-page
 ms.custom: "updateeachrelease"
-ms.date: 06/22/2022
+ms.date: 11/08/2022
 ---
 # .NET API browser
 

diff --git a/...icroservice-net-applications/rabbitmq-event-bus-development-test-environment.md b/...icroservice-net-applications/rabbitmq-event-bus-development-test-environment.md
@@ -114,7 +114,7 @@ A production-ready solution with support for RabbitMQ.
 
 - **NServiceBus** - Fully-supported commercial service bus with advanced management and monitoring tooling for .NET \
   <https://particular.net/>
-  
+
 - **EasyNetQ** - Open Source .NET API client for RabbitMQ \
   <https://easynetq.com/>
 

diff --git a/docs/azure/includes/dotnet-all.md b/docs/azure/includes/dotnet-all.md
diff --git a/docs/azure/includes/dotnet-new.md b/docs/azure/includes/dotnet-new.md
diff --git a/docs/core/compatibility/aspnet-core/7.0/wasm-app-authentication.md b/docs/core/compatibility/aspnet-core/7.0/wasm-app-authentication.md
@@ -7,7 +7,7 @@ ms.date: 10/20/2022
 
 We updated the support for authentication in Blazor WebAssembly apps to rely on the history state instead of query strings in the URL. As a result, existing applications that pass the return URL through the query string will fail to redirect back to the original page after a successful login.
 
-Existing applications should use the new <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.NavigationManagerExtensions.NavigateToLogout%2A> extension method as it's able to flow the data to the login page correctly.
+Existing applications should use the new <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.NavigationManagerExtensions.NavigateToLogin%2A> extension method as it's able to flow the data to the login page correctly.
 
 ## Version introduced
 
@@ -51,3 +51,7 @@ Most apps have a *RedirectToLogin.razor* file that you can update as follows:
 ## Affected APIs
 
 - <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.SignOutSessionStateManager?displayProperty=fullName> (obsoleted in favor of new <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.NavigationManagerExtensions.NavigateToLogout%2A?displayProperty=nameWithType> method)
+
+## See also
+
+- [RedirectToLogin component - Blazor WebAssembly](/aspnet/core/blazor/security/webassembly/standalone-with-authentication-library?view=aspnetcore-7.0&tabs=visual-studio#redirecttologin-component)
diff --git a/docs/core/deploying/deploy-with-cli.md b/docs/core/deploying/deploy-with-cli.md
@@ -3,7 +3,7 @@ title: Publish apps with the .NET CLI
 description: Learn to publish a .NET application using the .NET CLI commands.
 author: adegeo
 ms.author: adegeo
-ms.date: 03/30/2022
+ms.date: 11/08/2022
 ms.custom: updateeachrelease
 dev_langs:
   - "csharp"
@@ -31,6 +31,7 @@ Looking for some quick help on using the CLI? The following table shows some exa
 |                                                                   | 3.1         | `dotnet publish -c Release -r <RID> --self-contained true`                                 |
 |                                                                   | 5.0         | `dotnet publish -c Release -r <RID> --self-contained true`                                 |
 |                                                                   | 6.0         | `dotnet publish -c Release -r <RID> --self-contained true`                                 |
+|                                                                   | 7.0         | `dotnet publish -c Release -r <RID> --self-contained true`                                 |
 
 \* When using **SDK version 3.1** or higher, framework-dependent executable is the default publishing mode when running the basic `dotnet publish` command.
 
@@ -122,6 +123,7 @@ Publishing an FDD creates an app that automatically rolls-forward to the latest
 |                                | 3.1         | `dotnet publish -c Release -p:UseAppHost=false`             |
 |                                | 5.0         | `dotnet publish -c Release -p:UseAppHost=false`             |
 |                                | 6.0         | `dotnet publish -c Release -p:UseAppHost=false`             |
+|                                | 7.0         | `dotnet publish -c Release -p:UseAppHost=false`             |
 
 ## Framework-dependent executable
 
@@ -146,6 +148,7 @@ For .NET 2.1, you must use the following switches with the `dotnet publish` comm
 | Framework-dependent executable | 3.1         | `dotnet publish -c Release -r <RID> --self-contained false`<br>`dotnet publish -c Release` |
 |                                | 5.0         | `dotnet publish -c Release -r <RID> --self-contained false`<br>`dotnet publish -c Release` |
 |                                | 6.0         | `dotnet publish -c Release -r <RID> --self-contained false`<br>`dotnet publish -c Release` |
+|                                | 7.0         | `dotnet publish -c Release -r <RID> --self-contained false`<br>`dotnet publish -c Release` |
 
 Whenever you use the `-r` switch, the output folder path changes to: `./bin/<BUILD-CONFIGURATION>/<TFM>/<RID>/publish/`
 
@@ -174,9 +177,10 @@ You must use the following switches with the `dotnet publish` command to publish
 |                                | 3.1         | `dotnet publish -c Release -r <RID> --self-contained true`  |
 |                                | 5.0         | `dotnet publish -c Release -r <RID> --self-contained true`  |
 |                                | 6.0         | `dotnet publish -c Release -r <RID> --self-contained true`  |
+|                                | 7.0         | `dotnet publish -c Release -r <RID> --self-contained true`  |
 
 > [!TIP]
-> In .NET 6 you can reduce the total size of compatible self-contained apps by [publishing trimmed](trimming/trim-self-contained.md). This enables the trimmer to remove parts of the framework and referenced assemblies that are not on any code path or potentially referenced in [runtime reflection](../../csharp/programming-guide/concepts/reflection.md). See [trimming incompatibilities](./trimming/incompatibilities.md) to determine if trimming makes sense for your application.
+> In .NET 6 and later versions, you can reduce the total size of compatible self-contained apps by [publishing trimmed](trimming/trim-self-contained.md). This enables the trimmer to remove parts of the framework and referenced assemblies that are not on any code path or potentially referenced in [runtime reflection](../../csharp/programming-guide/concepts/reflection.md). See [trimming incompatibilities](./trimming/incompatibilities.md) to determine if trimming makes sense for your application.
 
 > [!NOTE]
 > You can reduce the total size of your deployment by enabling **globalization invariant mode**. This mode is useful for applications that are not globally aware and that can use the formatting conventions, casing conventions, and string comparison and sort order of the [invariant culture](xref:System.Globalization.CultureInfo.InvariantCulture). For more information about **globalization invariant mode** and how to enable it, see [.NET Core Globalization Invariant Mode](https://github.com/dotnet/runtime/blob/main/docs/design/features/globalization-invariant-mode.md).

diff --git a/docs/core/diagnostics/dotnet-trace.md b/docs/core/diagnostics/dotnet-trace.md
@@ -57,6 +57,10 @@ The `dotnet-trace` tool:
 - **`--version`**
 
   Displays the version of the dotnet-trace utility.
+
+- **`--duration`**
+
+  How log to run the trace. `--duration 00:00:00:05` will run it for 5 seconds.
 
 ## Commands
 
@@ -70,13 +74,13 @@ The `dotnet-trace` tool:
 
 ## dotnet-trace collect
 
-Collects a diagnostic trace from a running process or launches a child process and traces it (.NET 5+ only). To have the tool run a child process and trace it from its startup, append `--` to the collect command.
+Collects a diagnostic trace from a running process or launches a child process and traces it (.NET 5 or later). To have the tool run a child process and trace it from its startup, append `--` to the collect command.
 
 ### Synopsis
 
 ```dotnetcli
 dotnet-trace collect [--buffersize <size>] [--clreventlevel <clreventlevel>] [--clrevents <clrevents>]
-    [--format <Chromium|NetTrace|Speedscope>] [-h|--help]
+    [--format <Chromium|NetTrace|Speedscope>] [-h|--help] [--duration dd:hh:mm:ss]
     [-n, --name <name>] [--diagnostic-port] [-o|--output <trace-file-path>] [-p|--process-id <pid>]
     [--profile <profile-name>] [--providers <list-of-comma-separated-providers>]
     [--show-child-io]
@@ -151,6 +155,10 @@ dotnet-trace collect [--buffersize <size>] [--clreventlevel <clreventlevel>] [--
 - **`--diagnostic-port <path-to-port>`**
 
   The name of the diagnostic port to create. See [Use diagnostic port to collect a trace from app startup](#use-diagnostic-port-to-collect-a-trace-from-app-startup) to learn how to use this option to collect a trace from app startup.
+
+- **`--duration <time-to-run>`**
+
+  The time for the trace to run. Use the `dd:hh:mm:ss` format. For example `00:00:00:05` will run it for 5 seconds.
 
 - **`-o|--output <trace-file-path>`**
 
@@ -182,7 +190,7 @@ dotnet-trace collect [--buffersize <size>] [--clreventlevel <clreventlevel>] [--
 
   To learn more about some of the well-known providers in .NET, refer to [Well-known Event Providers](./well-known-event-providers.md).
 
-- **`-- <command>` (for target applications running .NET 5 only)**
+- **`-- <command>` (for target applications running .NET 5 or later)**
 
   After the collection configuration parameters, the user can append `--` followed by a command to start a .NET application with at least a 5.0 runtime. This may be helpful when diagnosing issues that happen early in the process, such as startup performance issue or assembly loader and binder errors.
 

diff --git a/docs/core/extensions/caching.md b/docs/core/extensions/caching.md
@@ -3,15 +3,15 @@ title: Caching in .NET
 description: Learn how to use various in-memory and distributed caching mechanisms in .NET.
 author: IEvangelist
 ms.author: dapine
-ms.date: 12/08/2021
+ms.date: 11/09/2022
 ---
 
 # Caching in .NET
 
 In this article, you'll learn about various caching mechanisms. Caching is the act of storing data in an intermediate-layer, making subsequent data retrievals faster. Conceptually, caching is a performance optimization strategy and design consideration. Caching can significantly improve app performance by making infrequently changing (or expensive to retrieve) data more readily available. This article introduces the two primary types of caching, and provides sample source code for both:
 
-- [`Microsoft.Extensions.Caching.Memory`](/dotnet/api/microsoft.extensions.caching.memory)
-- [`Microsoft.Extensions.Caching.Distributed`](/dotnet/api/microsoft.extensions.caching.distributed)
+- [Microsoft.Extensions.Caching.Memory](/dotnet/api/microsoft.extensions.caching.memory)
+- [Microsoft.Extensions.Caching.Distributed](/dotnet/api/microsoft.extensions.caching.distributed)
 
 > [!IMPORTANT]
 > There are two `MemoryCache` classes within .NET, one in the `System.Runtime.Caching` namespace and the other in the `Microsoft.Extensions.Caching` namespace:
@@ -25,7 +25,7 @@ All of the `Microsoft.Extensions.*` packages come dependency injection (DI) read
 
 ## In-memory caching
 
-In this section, you'll learn about the [`Microsoft.Extensions.Caching.Memory`](/dotnet/api/microsoft.extensions.caching.memory) package. The current implementation of the <xref:Microsoft.Extensions.Caching.Memory.IMemoryCache> is a wrapper around the <xref:System.Collections.Concurrent.ConcurrentDictionary%602>, exposing a feature-rich API. Entries within the cache are represented by the <xref:Microsoft.Extensions.Caching.Memory.ICacheEntry>, and can be any `object`. The in-memory cache solution is great for apps that run in a single server, where all the cached data rents memory in the app's process.
+In this section, you'll learn about the [Microsoft.Extensions.Caching.Memory](/dotnet/api/microsoft.extensions.caching.memory) package. The current implementation of the <xref:Microsoft.Extensions.Caching.Memory.IMemoryCache> is a wrapper around the <xref:System.Collections.Concurrent.ConcurrentDictionary%602>, exposing a feature-rich API. Entries within the cache are represented by the <xref:Microsoft.Extensions.Caching.Memory.ICacheEntry>, and can be any `object`. The in-memory cache solution is great for apps that run on a single server, where all the cached data rents memory in the app's process.
 
 > [!TIP]
 > For multi-server caching scenarios, consider the [Distributed caching](#distributed-caching) approach as an alternative to in-memory caching.
@@ -200,7 +200,7 @@ In the preceding C# code:
 - The `CacheSignal<T>` class is registered with <xref:Microsoft.Extensions.DependencyInjection.ServiceCollectionServiceExtensions.AddSingleton%2A>.
 - The `host` is instantiated from the builder, and started asynchronously.
 
-The `PhotoService` is responsible for getting photos that match a given criteria (or `filter`):
+The `PhotoService` is responsible for getting photos that match given criteria (or `filter`):
 
 :::code source="snippets/caching/memory-worker/PhotoService.cs":::
 
@@ -212,7 +212,7 @@ In the preceding C# code:
   - Calls and waits for the `_cacheSignal.WaitAsync()` to release, this ensures that the cache is populated before accessing the cache.
   - Calls `_cache.GetOrCreateAsync()`, asynchronously getting all of the photos in the cache.
   - The `factory` argument logs a warning, and returns an empty photo array - this should never happen.
-  - Each photo in the cache is iterated, filtered and materialized with `yield return`.
+  - Each photo in the cache is iterated, filtered, and materialized with `yield return`.
   - Finally, the cache signal is reset.
 
 Consumers of this service are free to call `GetPhotosAsync` method, and handle photos accordingly. No `HttpClient` is required as the cache contains the photos.
@@ -301,7 +301,7 @@ There are several convenience-based extension methods for reading values, that h
 
 #### Update values
 
-There is no way to actually update the values in the distributed cache with a single API call, instead values can have their sliding expirations reset with one of the refresh APIs:
+There is no way to update the values in the distributed cache with a single API call, instead, values can have their sliding expirations reset with one of the refresh APIs:
 
 - <xref:Microsoft.Extensions.Caching.Distributed.IDistributedCache.RefreshAsync%2A?displayProperty=nameWithType>
 - <xref:Microsoft.Extensions.Caching.Distributed.IDistributedCache.Refresh%2A?displayProperty=nameWithType>

diff --git a/docs/core/extensions/channels.md b/docs/core/extensions/channels.md
@@ -3,7 +3,7 @@ title: Channels
 description: Learn how to use System.Threading.Channels in .NET.
 author: IEvangelist
 ms.author: dapine
-ms.date: 08/03/2022
+ms.date: 11/09/2022
 ---
 
 # System.Threading.Channels library

diff --git a/docs/core/extensions/configuration-providers.md b/docs/core/extensions/configuration-providers.md
@@ -3,7 +3,7 @@ title: Configuration providers
 description: Learn how the Configuration provider API is used to configure .NET applications.
 author: IEvangelist
 ms.author: dapine
-ms.date: 10/12/2022
+ms.date: 11/09/2022
 ms.topic: reference
 ---
 

diff --git a/docs/core/extensions/configuration.md b/docs/core/extensions/configuration.md
@@ -3,7 +3,7 @@ title: Configuration
 description: Learn how to use the Configuration API to configure .NET applications.
 author: IEvangelist
 ms.author: dapine
-ms.date: 11/19/2021
+ms.date: 11/09/2022
 ms.topic: overview
 ---