Merge pull request #35449 from dotnet/main

Merge to Live

Author: Rick-Anderson

aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md

@@ -498,8 +498,8 @@ Use `InvokeNew(string identifier, object?[]? args)` on <xref:Microsoft.JSInterop
 ```csharp
 var inProcRuntime = ((IJSInProcessRuntime)JSRuntime);
 var classRef = inProcRuntime.InvokeNew("TestClass", "Blazor!");
-var text = await classRef.GetValueAsync<string>("text");
-var textLength = await classRef.InvokeAsync<int>("getTextLength");
+var text = classRef.GetValue<string>("text");
+var textLength = classRef.Invoke<int>("getTextLength");
 ```
 
 An overload is available that takes a <xref:System.Threading.CancellationToken> argument or <xref:System.TimeSpan> timeout argument.

aspnetcore/release-notes/aspnetcore-10.0.md

@@ -53,9 +53,13 @@ This section describes new features for OpenAPI.
 
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/webapiaotTemplateAddedOpenAPI.md)]
 
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/doc-provider-in-di.md)]
+
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/xml-comment-generator.md)]
+
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiSchemasInTransformers.md)]
 
-## Authentication and authorization
+### Authentication and authorization
 
 This section describes new features for authentication and authorization.
 

aspnetcore/release-notes/aspnetcore-10/includes/doc-provider-in-di.md

@@ -1,6 +1,7 @@
 ## Support for IOpenApiDocumentProvider in the DI container.
-<!-- https://github.com/dotnet/aspnetcore/pull/61463 -->
-ASP.NET has added support for `IOpenApiDocumentProvider` in the DI container.
-This allows you to inject the `IOpenApiDocumentProvider` into your application and use it to access the OpenAPI document.
-This is useful for scenarios where you need to access the OpenAPI document outside of the context of an HTTP request,
-such as in a background service or a custom middleware.
+
+ASP.NET Core in .NET 10 supports [IOpenApiDocumentProvider](https://source.dot.net/#Microsoft.AspNetCore.OpenApi/Services/IOpenApiDocumentProvider.cs) in the dependency injection (DI) container. Developers can inject `IOpenApiDocumentProvider` into their apps and use it to access the OpenAPI document. This approach is useful for accessing OpenAPI documents outside the context of HTTP requests, such as in background services or custom middleware.
+
+Previously, running application startup logic without launching an HTTP server could be done by using `HostFactoryResolver` with a no-op `IServer` implementation. The new feature simplifies this process by providing a streamlined API inspired by Aspire's <xref:Aspire.Hosting.Publishing.IDistributedApplicationPublisher>, which is part of Aspire's framework for distributed application hosting and publishing. For more information, see [Aspire Documentation](https://aspire.example.com/docs/distributed-application-publisher).
+
+

aspnetcore/release-notes/aspnetcore-10/includes/xml-comment-generator.md

@@ -1,12 +1,12 @@
-## Improvements to XML comment generator
+### Improvements to the XML comment generator
 
-<!-- https://github.com/dotnet/aspnetcore/pull/61145 -->
+XML comment generation handles complex types in .NET 10 better than earlier versions of .NET.
 
-<!-- it should throw fewer build errors now.
-- It should also work with the Identity API XML comments but I haven't verified that.
-  - Maybe update docs about failure mode. -->
+* It produces accurate and complete XML comments for a wider range of types.
+* It handles more complex scenarios.
+* It gracefully bypasses processing for complex types that cause build errors in earlier versions.
 
-The XML comment generator has been enhanced to better handle complex types. In conjunction, the generator now gracefully bypasses processing for complex types that previously caused build errors. Taken together, these changes improve the robustness of XML comment generation but change the failure mode for certain scenarios from build errors to missing metadata.
+These improvements change the failure mode for certain scenarios from build errors to missing metadata.
 
 In addition, XML doc comment processing can now be configured to access XML comments in other assemblies. This is useful for generating documentation for types that are defined outside the current assembly, such as the `ProblemDetails` type in the `Microsoft.AspNetCore.Http` namespace.
 
@@ -15,14 +15,16 @@ This configuration is done with directives in the project build file. The follow
 ```xml
 <Target Name="AddOpenApiDependencies" AfterTargets="ResolveReferences">
   <ItemGroup>
-    <!-- Include XML documentation from Microsoft.AspNetCore.Http.Abstractions to get metadata for ProblemDetails -->
+  <!-- Include XML documentation from Microsoft.AspNetCore.Http.Abstractions
+    to get metadata for ProblemDetails -->
     <AdditionalFiles
-          Include="@(ReferencePath->'%(RootDir)%(Directory)%(Filename).xml')"
-          Condition="'%(ReferencePath.Filename)' == 'Microsoft.AspNetCore.Http.Abstractions'"
+          Include="@(ReferencePath->'
+            %(RootDir)%(Directory)%(Filename).xml')"
+          Condition="'%(ReferencePath.Filename)' ==
+           'Microsoft.AspNetCore.Http.Abstractions'"
           KeepMetadata="Identity;HintPath" />
   </ItemGroup>
 </Target>
 ```
 
 We expect to include XML comments from a selected set of assemblies in the shared framework in future previews, to avoid the need for this configuration in most cases.
-<!--[!INCLUDE[](~/release-notes/aspnetcore-10/includes/xml-comment-generation.md)] -->